Subject: Re: FYI: Fix for (non-IPsec) IPv6 with FAST_IPSEC
To: Jonathan Stone <jonathan@dsg.stanford.edu>
From: Thor Lancelot Simon <tls@rek.tjls.com>
List: tech-security
Date: 04/26/2004 17:35:50
On Sun, Apr 25, 2004 at 07:54:44PM -0700, Jonathan Stone wrote:
> 
> As of now, NetBSD-current kernels with both ``options FAST_IPSEC' and
> ``options INET6'' should work, for IPv4 traffic with or without IPsec;
> and for IPv6 traffic without IPsec. (Attempts to IPsec IPv6 traffic
> just plain don't work: they cause the traffic to be output as
> cleartext, and blackholed on reception).

Violating the security policy on output is *very* bad.

If the code can't be changed to actually encrypt the packets, it should
at least blackhole them on output -- always.  If it can't be changed to
blackhole them, it should be changed to refuse to allow such security
policy rules to be loaded, to emit a loud, obvious warning when a kernel
is so configured, and to emit a loud, obvious warning when such a kernel
is booted.

Silently emitting unencrypted traffic that the user expected to be
encrypted is *really* bad.

Thor