lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B2029A1.5010404@hp.com>
Date:	Wed, 09 Dec 2009 17:50:09 -0500
From:	Brian Haley <brian.haley@...com>
To:	Chuck Lever <chuck.lever@...cle.com>
CC:	Jeff Layton <jlayton@...hat.com>,
	Linux Network Developers <netdev@...r.kernel.org>
Subject: Re: IPv6: presentation format for zero scope ID

Hi Chuck,

Chuck Lever wrote:
>> So this means that addresses with those prefixes should be treated like
>> any other address, right? If so, then I think the rpc_ntop6 shouldn't be
>> affixing scopeid's to site local addresses.
> 
> As a final detail, we're trying to understand what is the correct
> treatment for site-local addresses.  I've looked at RFC 3879.  In
> late-model Linux kernels, is Jeff's interpretation correct, for
> application layer protocols like RPC?

Not sure if this answers the question, but recent Linux kernels only look
at the scope ID for link-local addresses.

-Brian
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ