netdev - CONFIG_NET_KEY defaults to N

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]

Message-ID: <19f34abd0807220952g6bef12aeufe1abddeb1c3fbad@mail.gmail.com>
Date:	Tue, 22 Jul 2008 18:52:14 +0200
From:	"Vegard Nossum" <vegard.nossum@...il.com>
To:	netdev@...r.kernel.org
Subject: CONFIG_NET_KEY defaults to N

Hi,

There's one thing I keep wondering about:

CONFIG_NET_KEY has this help text:

  │ PF_KEYv2 socket family, compatible to KAME ones.
  │ They are required if you are going to use IPsec tools ported
  │ from KAME.
  │
  │ Say Y unless you know what you are doing.

It defaults to N, however.

Which one is wrong, the help-text or the default? Should it be changed?

Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036