netdev - Re: IPv6 address printf format specifier

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] [day] [month] [year] [list]

Message-Id: <2810B800-C22B-4EB6-97FC-80FBDCD955FE@oracle.com>
Date:	Thu, 19 Mar 2009 12:11:27 -0400
From:	Chuck Lever <chuck.lever@...cle.com>
To:	David Miller <davem@...emloft.net>, vladislav.yasevich@...com
Cc:	netdev@...r.kernel.org
Subject: Re: IPv6 address printf format specifier

On Mar 19, 2009, at Mar 19, 2009, 1:30 AM, David Miller wrote:
> From: Vlad Yasevich <vladislav.yasevich@...com>
> Date: Wed, 18 Mar 2009 22:26:30 -0400
>
>> There are multiple different forms of presenting addresses, all of
>> which are valid and non of which will provide for sting equality.
>> Regardless of how we represent our IPv6 addresses, there is a chance
>> that it will cause interoperability issues and the only way to truly
>> solve it is to change applications to compare addresses in their
>> true numerical representation.
>
> Or to, they themselves, canonicalize the text representation before
> comparison.

Thanks, this was helpful.

We had considered converting the string address to a sockaddr and back  
in user space, and that sounds like a good way to ensure we get the  
same presentation address for comparison.

--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
--
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