Bug#295731: ssh fails to bind link-scope IPv6 addresses

2006-12-11 Thread Rémi Denis-Courmont
Le dimanche 10 décembre 2006 23:15, vous avez écrit : Where did you get that syntax from? This is a fairly common getaddrinfo() hostname extension, present in at least GNU libc and BSD libc. Why do I have to specify the interface if only one such link-local address exists on the system?

Bug#295731: ssh fails to bind link-scope IPv6 addresses

2006-12-11 Thread Hendrik Sattler
Am Montag 11 Dezember 2006 12:02 schrieb Rémi Denis-Courmont: And again: where is this documented? Partly in RFC 3542. Otherwise in glibc source code. Ok, if this is a standard way, then that's valid behaviour. However, the words in the RFC are _not_ that specific: When the address is a

Bug#295731: ssh fails to bind link-scope IPv6 addresses

2006-12-11 Thread Rémi Denis-Courmont
Le lundi 11 décembre 2006 17:34, vous avez écrit : I agree with the problem on bridges but not on a normal system I cannot agree. It would really suck when the requirement for a scope ID would depend on the run-time configuration of the system, and the Linux kernel IPv6 implementors probably

Bug#295731: ssh fails to bind link-scope IPv6 addresses

2005-04-19 Thread Chaskiel M Grundman
# ssh -6 fe80::2xx:xxff:fexx: ssh: connect to host fe80::2xx:xxff:fexx: port 22: Invalid argument This is not a bug in sshd. It is arguably a bug in the ssh client. Since any given link-local address can potentially exist on all non-loopback interfaces on a host, you need to identify

Bug#295731: ssh fails to bind link-scope IPv6 addresses

2005-02-17 Thread Hendrik Sattler
Package: ssh Version: 1:3.8.1p1-8.sarge.4 Severity: important Hi, I try to setup IPv6 on my local network. Ping6 already works but sshd refuses to cooperate: # sshd -d -e debug1: sshd version OpenSSH_3.8.1p1 Debian-8.sarge.4 debug1: private host key: #0 type 0 RSA1 debug1: read PEM private key