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

Date:	Mon, 16 Mar 2009 12:24:29 -0400
From:	Chuck Lever <chuck.lever@...cle.com>
To:	netdev@...r.kernel.org
Subject: IPv6 address printf format specifier

The NFS and RPC code in the kernel now uses the new printf format  
specifier for IPv6 addresses.  In some cases, the generated address  
string is sent out of the kernel (for example, it is used to build a  
universal address for RPCB_SET requests, and used as the mon_name in  
some SM_MON upcalls to our rpc.statd).

The problem is that outside the kernel, applications generally use  
getnameinfo(3) or inet_ntop(3) to do this conversion.  The library  
follows the RFC suggestion of shortening these address strings by  
replacing the longest series of zeroes in the IPv6 address with "::".

Since the kernel doesn't do that, string comparisons don't work when  
comparing address strings that came from our kernel.  Since these  
address strings appear to other hosts (via the rpcbind registry) this  
is, or could become, an interoperability issue for Linux.

How should I fix this?

1.  Copy glibc's code to the printf logic for %pI6

2.  Copy glibc's code to a special function used only by SM_MON and  
RPCB_SET

3.  Other suggestions or preferences?

Glibc's implementation is Paul Vixie's free version.

--
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