netdev - [IPv6] Why does IPV6_ROUTE_INFO still depends on EXPERIMENTAL?

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

Date:	Wed, 13 Jul 2011 00:03:21 +0200
From:	"Stefan (metze) Metzmacher" <metze@...ba.org>
To:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: [IPv6] Why does IPV6_ROUTE_INFO still depends on EXPERIMENTAL?

Hi,

I'm wondering why IPV6_ROUTE_INFO still depends on EXPERIMENTAL about
5 years after the initial implementation?

I'm also wondering why IPV6_PRIVACY, IPV6_ROUTER_PREF, IPV6_ROUTE_INFO
are compile time switches at all, while there're runtime switches which
are of
by default.

It would be nice to have more IPv6 features enabled (at compile time) by
default,
so that features can be turned (at runtime) with default distribution
kernels.

Is there a chance get patches accepted, which remove some compile time
switches?

metze

Download attachment "signature.asc" of type "application/pgp-signature" (263 bytes)