On Mon, Dec 29, 2008 at 5:01 PM, Jan-Oliver Wagner <jan-oliver.wag...@intevation.de> wrote: > On Montag, 29. Dezember 2008, Stjepan Gros wrote:
>> but what caught my attention was the mention of IPv6. It turns out >> that OpenVAS doesn't support it? Is it true? > > I'd be thankful if anyone could clearly define or specify what "IPv6 Support > in OpenVAS" > is or should be. So far I received only foggy answers. It could mean few things: 1. It means that you can enter IPv6 address(es) in the OpenVAS client and then those hosts, whith those addresses, are scanned. This is not so simple as just entering IPv6 address because the socket code is different: - for a start, addresses are stored in sockaddr_in6 structure instead of sockaddr_in - AF_INET6 has to be used in place of AF_INET (e.g. creating socket, converting ascii adresses with inet_pton/inet_ntop) - constants like INADDR_ANY can not be used with IPv6 after the socket is created and bound (or connected) I believe it doesn't matter any more if IPv4 or IPv6 is used. 2. It means that when you enter hostname (or FQDN) which resolves to IPv6 address, this address will be used 3. There is a code in openvas for forging IP packets. This code has to be enhanced to know how to construct IPv6 packets. 4. NASL laguage has to be enhanced to accept IPv6 addresses, and potentially IPv6 specific extensions. And IMHO, with all the recent hype around IPv4 address shortages, and IPv6 mandatory use, and a like, i think that it would be good to introduce IPv6 as soon as possible, but that obviously won't be easy. > Once clarified (a CR perhaps), I am more than willing to invest time/money > into this > feature. SG _______________________________________________ Openvas-devel mailing list Openvas-devel@wald.intevation.org http://lists.wald.intevation.org/mailman/listinfo/openvas-devel
