On Sun, 24 Sep 2000, Jason Gunthorpe wrote: > On Sun, 24 Sep 2000, Henrique M Holschuh wrote: > > dealing with ipv6... especially those packages which the ipv6 porters didn't > > have a look at and for which upstream does not provide ipv6 support > > out-of-the-box. That's what I should have said in my first post :-( > > There is no such thing. Any application right now that does not support > ipv6 will not magically start supporting it. The APIs are not compatible > at the source level (unless you use RFC 2553, which AFAIK is only used by > ipv6 people) Well, that's comforting to know :-) As I said, I'm not well versed in ipv4 x ipv6 socket programming. If a ipv4 app/daemon will NEVER manage to have ipv6 data thrown at it where it expected ipv4 and still partially work (managing to bind a ipv6 socket for listening, or connecting to a ipv6 host using a ipv6 IP), but fail to correctly validate the IP or reverse DNS against its access control lists because it only knows ipv4... then there's no pressing need for any extra audits. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
Attachment:
pgpHKH_AwyPLv.pgp
Description: PGP signature