This is the mail archive of the libc-help@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Adding AF_VSOCK to getaddrinfo(3)


On 08/14/2015 04:44 PM, Stefan Hajnoczi wrote:

> Represent AF_VSOCK <uint32_t cid, uint32_t port> addresses textually as
> node "[vsock:<cid>]" and service "<port>".  For example, cid 2 and port
> 80
> is written as node "[vsock:2]" and service "80".
> 
> This is close to the IPv6 notation but not a valid IPv6 address, so it's
> possible to extend address parsing code to handle the AF_VSOCK case.

What's your use case for this functionality?

How transparent do you want to the implementation to be?  Returning
AF_VSOCK addresses for AF_UNSPEC queries would give instant AF_VSOCK
support to many applications, but could also have unforseen security
consequences.

-- 
Florian Weimer / Red Hat Product Security


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]