similar to: [Bug 1602] New: ssh: doesn't handle IPv6 addresses with brackets

https://bugzilla.mindrot.org/show_bug.cgi?id=1602 --- Comment #6 from Marc Herbert <marc.herbert+mindrot at gmail.com> --- Just did some more testing with OpenSSH_8.1p1 Apr 2020. It looks like someone did the work to implement a new ssh://[brackets] syntax except in the case where brackets are actually needed. Baffling. So these now work: ssh ssh://[host.local]:23 ssh

https://bugzilla.mindrot.org/show_bug.cgi?id=1602 Marc Herbert <marc.herbert+mindrot at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX |--- --- Comment #7 from Marc Herbert

https://bugzilla.mindrot.org/show_bug.cgi?id=1602 Marc Herbert <marc.herbert+mindrot at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marc.herbert+mindrot at gmail. | |com --- Comment #1

https://bugzilla.mindrot.org/show_bug.cgi?id=1602 --- Comment #8 from Marc Herbert <marc.herbert+mindrot at gmail.com> --- Fun fact: ssh _does_ produce brackets for IPv6 addresses in .ssh/known_hosts: [review.openstack.org]:29418,[104.130.246.32]:29418 ssh-rsa AAAAB3NzaC1yc2... [review.openstack.org]:29418,[2001:4800:7819:103:be76:4eff:fe04:9229]:29418 ssh-rsa AAAAB3Nza... But it

https://bugzilla.mindrot.org/show_bug.cgi?id=1602 Darren Tucker <dtucker at dtucker.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dtucker at dtucker.net --- Comment #9 from Darren Tucker <dtucker at dtucker.net> --- (In reply to Marc

https://bugzilla.mindrot.org/show_bug.cgi?id=1602 --- Comment #10 from Marc Herbert <marc.herbert+mindrot at gmail.com> --- Still failing: ssh -V OpenSSH_9.6p1, OpenSSL 3.2.1 30 Jan 2024 ssh ::1 # OK ssh [::1] # Could not resolve hostname [::1] ssh ssh://[127.0.0.1] # Woks!? ssh ssh://[::1] # prints usage message Ridiculously inconsistent. PS: port

https://bugzilla.mindrot.org/show_bug.cgi?id=1734 Summary: IPv6 address in port forward options (-L) requires square brackets Product: Portable OpenSSH Version: 5.4p1 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P2 Component: ssh AssignedTo:

https://bugzilla.mindrot.org/show_bug.cgi?id=3161 Bug ID: 3161 Summary: ssh -J <public IPv6> <LL IPv6%scopeID> doesn't work as expected Product: Portable OpenSSH Version: 8.2p1 Hardware: 68k OS: Mac OS X Status: NEW Severity: enhancement Priority: P5

https://bugzilla.mindrot.org/show_bug.cgi?id=2258 Bug ID: 2258 Summary: Add hint to IPv6 syntax Product: Portable OpenSSH Version: 6.6p1 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: scp Assignee: unassigned-bugs at mindrot.org

Hello, I'd like to remove the individual pairs of square brackets along with their content - plus the space directly behind it - from address strings such as this: [Swidsinski, Alexander; Loening-Baucke, Vera; Lochs, Herbert] Charite Humboldt Univ, Innere Klin, D-10098 Berlin, Germany; [Hale, Laura P.] Duke Univ, Med Ctr, Dept Pathol, Durham, NC 27710 USA I'd like get the

https://bugzilla.mindrot.org/show_bug.cgi?id=1734 Marc Herbert <marc.herbert+mindrot at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marc.herbert+mindrot at gmail. | |com --- Comment #6

Hello, when I have this in /etc/sysconfig/network-scripts/ifcfg-eth0 TYPE=Ethernet NAME=eth0 NM_CONTROLLED=no ONBOOT=yes DEVICE=eth0 USERCTL=no ... IPV6INIT=yes IPV6ADDR=2001:DB8:DEAD:BEEF::10 IPV6ADDR_SECONDARIES="2001:DB8:DEAD:BEEF::20 2001:DB8:DEAD:BEEF::30 2001:DB8:DEAD:BEEF::40 2001:DB8:DEAD:BEEF::50" IPV6_AUTOCONF=no IPV6_DEFAULTGW=2001:DB8:DEAD:BEEF::1 IPV6_DEFAULTDEV=eth0 I

Hi I used the command "ip -6 addr add 2001:DB8:CAFE:1111::12/64 dev eth0" to add ipv6 address and can see it in ifconfig but can't ping it Why? Thank you # ping6 2001:db8:cafe:1111::12 PING 2001:db8:cafe:1111::12(2001:db8:cafe:1111::12) 56 data bytes >From ::1 icmp_seq=1 Destination unreachable: Address unreachable >From ::1 icmp_seq=2 Destination unreachable: Address

Dear R Helpers, I came across discrepancies in estimates for nested factors in linear models computed with brackets and also when a crossing factor is defined as a factor or as a dummy (0/1) vector. These are probably designed features that I do not understand. I wonder if someone would be so kind as to explain them to me. First, if I do not bracket the nested pair of factors A/C, then (1) I

Commit-ID: 08e03dee1485ec4823b3afd465b32938b3a40045 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=08e03dee1485ec4823b3afd465b32938b3a40045 Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Sat, 3 Sep 2016 21:58:50 +0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 25 Jan 2019 02:57:21 +0000 [klibc] expand - Fix dangling

Commit-ID: 9885e7650e5daf90ddc2a9bb1dfc6af14e86ad9d Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=9885e7650e5daf90ddc2a9bb1dfc6af14e86ad9d Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Sat, 3 Sep 2016 21:58:50 +0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 28 Mar 2020 21:42:54 +0000 [klibc] dash: expand - Fix

Hello I've got two prefixes, one /48 and one /64 let's say these two 2001:db8:0815::/48 2001:db8:4711:cafe::/64 the router has on it's ethernet interface the following to IPv6 addresses: 2001:db8:0815::1/48 2001:db8:4711:cafe::1/64 a windows box has 2001:db8:0815::17/48 and 2001:db8:0815::1 as it's gateway a linux box has 2001:db8:4711:cafe::11/64 and 2001:db8:4711:cafe::1 as

On Wed, 2024-03-13 at 11:41 +0000, Job Snijders wrote: > On Wed, Mar 13, 2024 at 12:19:24PM +0100, Adam Kalisz wrote: > > it seems I cannot use: > > > > $ ssh -J root at 2a01:4f8:1c1e:528d::1 root at west-coast > > Invalid -J argument > > Try this: > > ??? $ ssh -J root@[2a01:4f8:1c1e:528d::1] root at west-coast Thank you all for helping with the syntax.

Hi, I have three squeeze servers running: ii linux-image-2.6.32-5-xen-amd64 2.6.32-38 Linux 2.6.32 for 64-bit PCs, Xen dom0 support ii xen-hypervisor-4.0-amd64 4.0.1-4 The Xen Hypervisor on AMD64 All three servers have Intel gigabit NICs, but one server uses the e1000e driver and the other two use the igb driver. They've been in production for around 6 months now

Hi, I have three Debian squeeze servers running: ii linux-image-2.6.32-5-xen-amd64 2.6.32-38 Linux 2.6.32 for 64-bit PCs, Xen dom0 support ii xen-hypervisor-4.0-amd64 4.0.1-4 The Xen Hypervisor on AMD64 All three servers have Intel gigabit NICs, but one server uses the e1000e driver and the other two use the igb driver. They''ve been in production for around 6