From: Mike Fedyk <mfedyk@matchmail.com>
To: Dax Kelson <dax@gurulabs.com>
Cc: linux-kernel@vger.kernel.org, usagi-users-ctl@linux-ipv6.org,
linux-ipsec@freeswan.org
Subject: Re: Question: Status of USAGI/FreeSWAN?
Date: Thu, 10 May 2001 19:52:00 -0700 [thread overview]
Message-ID: <20010510195200.P26262@mikef-linux.matchmail.com> (raw)
In-Reply-To: <200105100253.f4A2rsK305959@saturn.cs.uml.edu> <Pine.SOL.4.30.0105100052440.10105-100000@ultra1.inconnect.com>
In-Reply-To: <Pine.SOL.4.30.0105100052440.10105-100000@ultra1.inconnect.com>; from dax@gurulabs.com on Thu, May 10, 2001 at 01:28:25AM -0600
On Thu, May 10, 2001 at 01:28:25AM -0600, Dax Kelson wrote:
>
> FreeSWAN has IPSec for IPv4 on Linux.
>
> USAGI is better/more conformant IPv6 (with IPSec for IPv6 in development)
> for Linux.
>
> The USAGI goal is to get themselves folded into the official kernel (and
> glibc) at some point "in the near future".
>
> What are the plans to get all this (FreeSWAN,USAGI) folded into the
> kernel. Are the "crypto" legal issues resolved enough now to have crypto
> in the official kernel? It would nice to not to have to chase down all
> these seperate components and eventually manually patch.
>
> I'm going a bit crazy keeping track of several different kernel patches
> (IPSec,IPv6 in particular) while my *BSD friends just laugh at me. :)
>
> Dax
>
You'll probably get more response if you don't reply to an anready existing
thread.
Just create another message with the exact above and try again without
replying...
Mike
next prev parent reply other threads:[~2001-05-11 2:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-09 20:17 Patch to make ymfpci legacy address 16 bits Pavel Roskin
2001-05-09 20:23 ` Jeff Garzik
2001-05-09 20:52 ` Pavel Roskin
2001-05-09 21:08 ` Jeff Garzik
2001-05-09 23:43 ` Pavel Roskin
2001-05-09 23:53 ` Zach Brown
2001-05-10 2:53 ` Albert D. Cahalan
2001-05-10 7:28 ` Question: Status of USAGI/FreeSWAN? Dax Kelson
2001-05-11 2:52 ` Mike Fedyk [this message]
2001-05-10 11:54 ` Patch to make ymfpci legacy address 16 bits mirabilos
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=20010510195200.P26262@mikef-linux.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=dax@gurulabs.com \
--cc=linux-ipsec@freeswan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=usagi-users-ctl@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox