Morning,
On 01-01-02 horape@tinuviel.compendium.net.ar wrote:
> > > > > Options are:
> > > > > (a) ListenAddress set: IPv4 works, IPv6 doesn't.
> > > > > (b) ListenAddress unset: IPv4 works the very same way, IPv6 works.
> > > > Would this cause first an IPv6 lookup for the IP and then a IPv4 lookup?
> > > [I assume lookup = dns lookup, else i don't understand the question]
> > Yes.
> > > No. That's a bind(2) call. There is no dns lookup anywhere.
> > Are you sure? I think there's also a dns-lookup involved as otherwise
> > you won't know the IP-address of the host that ssh should connect to.
> Remember that we're talking about the server. The dns lookups are done
But we also have to look at the effect for the users, because there are
some users that do ssh localhost and where IPv6 is not configured.
> just at connection time. The only dns lookup made by the server should
> be an inverse lookup against the address where the connection is originated
> from.
Sure, that it's not trying an IPv6 Lookup first and then doing an IPv4
Lookup if the first fails?
Ciao
Christian
--
Debian Developer and Quality Assurance Team Member
1024/26CC7853 31E6 A8CA 68FC 284F 7D16 63EC A9E6 67FF 26CC 7853
Attachment:
pgp2d7Vr_9ePh.pgp
Description: PGP signature