All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zach Brown <zab@zabbo.net>
To: "David S. Miller" <davem@redhat.com>
Cc: sandy@storm.ca, mk@linux-ipv6.org, linux-kernel@vger.kernel.org,
	design@lists.freeswan.org, usagi@linux-ipv6.org
Subject: Re: [Design] [PATCH] USAGI IPsec
Date: Fri, 18 Oct 2002 21:40:31 -0400	[thread overview]
Message-ID: <20021018214031.D22727@bitchcake.off.net> (raw)
In-Reply-To: <20021011.192750.85684324.davem@redhat.com>; from davem@redhat.com on Fri, Oct 11, 2002 at 07:27:50PM -0700

> It's fine for testing purposes, leave it in.

absolutely.  it could also be needed for interoperability, or many other
valid uses that might not depend on its sheer strength as a cipher.

"but you shouldn't be interoperating with things that are insecure!"

blah blah blah.  that is not the kernel's decision to make.  meaningful
security is defined by much more than context-free assertions.  warn
against its naive use, avoid it being a default, but allow the clued to
use it easily when it makes sense.

- z

  reply	other threads:[~2002-10-19  1:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-11  8:05 [PATCH] USAGI IPsec Mitsuru KANDA
2002-10-12 17:11 ` [Design] " Sandy Harris
2002-10-12  2:27   ` David S. Miller
2002-10-19  1:40     ` Zach Brown [this message]
2002-10-21 14:46 ` Sandy Harris
2002-10-21  2:41   ` David S. Miller
2002-10-21  3:42     ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-21  7:34     ` [CryptoAPI-devel] " Herbert Valerio Riedel
2002-10-22  2:27       ` Sandy Harris
2002-10-22  5:02       ` Jari Ruusu
2002-10-24 14:50         ` Jean-Luc Cooke
2002-10-28 13:55           ` JuanJo Ciarlante
2002-10-21  4:22   ` Andre Hedrick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021018214031.D22727@bitchcake.off.net \
    --to=zab@zabbo.net \
    --cc=davem@redhat.com \
    --cc=design@lists.freeswan.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mk@linux-ipv6.org \
    --cc=sandy@storm.ca \
    --cc=usagi@linux-ipv6.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.