From: Robert Love <rml@tech9.net>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Andreas Dilger <adilger@turbolabs.com>,
"Dennis, Jim" <jdennis@snapserver.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: crypto (was Re: Congrats Marcelo,)
Date: 26 Feb 2002 16:35:54 -0500 [thread overview]
Message-ID: <1014759355.1109.31.camel@phantasy> (raw)
In-Reply-To: <3C7BFAFA.D8923CFF@mandrakesoft.com>
In-Reply-To: <2D0AFEFEE711D611923E009027D39F2B153AD4@cdserv.meridian-data.com> <20020226140644.U12832@lynx.adilger.int> <3C7BFAFA.D8923CFF@mandrakesoft.com>
On Tue, 2002-02-26 at 16:15, Jeff Garzik wrote:
> I would -love- to see crypto in the mainstream kernel. Distribution of
> crypto software on kernel.org has been OK for a while now.
>
> Who knows what the kerneli guys, freeswan, etc. guys think.
>
> IMO it's time to get a good IPsec implementation in the kernel...
Besides IPsec, what crypto is there for the kernel? I've never really
understood what "crypto in the kernel means" since it all should be a
userspace thing.
Except IPsec, of course, and adding Freeswan would be a Good Thing.
Freeswan people?
One thing I've heard in the past is "Yes, the US is safe now wrt
encryption but <country> is not" -- and I've seen country=France,etc
i.e. (self) important places.
Robert Love
next prev parent reply other threads:[~2002-02-26 21:36 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 20:38 Congrats Marcelo, Dennis, Jim
2002-02-26 20:50 ` H. Peter Anvin
2002-02-26 21:06 ` Andreas Dilger
2002-02-26 21:15 ` crypto (was Re: Congrats Marcelo,) Jeff Garzik
2002-02-26 21:35 ` Robert Love [this message]
2002-02-26 21:40 ` arjan
2002-02-26 21:47 ` Robert Love
2002-02-24 23:51 ` Daniel Phillips
2002-02-28 22:32 ` Bill Davidsen
2002-03-01 9:50 ` Francois Romieu
2002-02-27 9:41 ` Francois Romieu
2002-02-26 22:33 ` Rik van Riel
2002-02-27 21:15 ` Michael H. Warfield
2002-02-27 21:57 ` Rik van Riel
2002-02-27 22:29 ` Michael H. Warfield
2002-02-27 23:06 ` Rik van Riel
2002-02-26 21:56 ` Congrats Marcelo, Steve Lord
2002-02-24 23:39 ` Daniel Phillips
2002-02-26 23:07 ` Steve Lord
2002-02-25 0:10 ` Daniel Phillips
2002-02-26 23:23 ` Rainer Ellinger
2002-02-25 0:38 ` Daniel Phillips
2002-02-26 23:59 ` Martin J. Bligh
2002-02-27 0:47 ` Rainer Ellinger
2002-02-27 1:03 ` Martin J. Bligh
2002-02-27 1:08 ` Matthew D. Pitts
2002-02-26 22:59 ` Alan Cox
2002-02-26 22:59 ` Steve Lord
2002-02-25 0:28 ` Whither XFS? (was: Congrats Marcelo) Daniel Phillips
2002-02-26 23:39 ` Steve Lord
2002-02-25 8:22 ` Daniel Phillips
2002-02-26 23:00 ` Congrats Marcelo, J.A. Magallon
2002-02-28 21:52 ` Marcelo Tosatti
2002-03-01 0:01 ` Alan Cox
2002-03-01 0:37 ` Dave Jones
2002-03-01 1:13 ` Alan Cox
2002-03-01 1:03 ` Dave Jones
2002-03-01 1:51 ` Alan Cox
2002-03-01 1:28 ` Theodore Tso
2002-03-01 1:53 ` Mike Fedyk
2002-03-02 22:35 ` Hans-Peter Jansen
2002-03-02 3:43 ` Stephen Degler
2002-02-28 22:41 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2002-02-26 23:18 crypto (was Re: Congrats Marcelo,) Dennis, Jim
2002-02-27 0:24 ` Chris Wright
2002-02-27 0:42 Dennis, Jim
2002-02-27 1:02 ` Chris Wright
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=1014759355.1109.31.camel@phantasy \
--to=rml@tech9.net \
--cc=adilger@turbolabs.com \
--cc=jdennis@snapserver.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox