From: Derek Atkins <warlord@MIT.EDU>
To: bert hubert <ahu@ds9a.nl>
Cc: Andreas Jellinghaus <aj@dungeon.inka.de>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: ipsec-tools 0.1 + kernel 2.5.64
Date: 05 Mar 2003 09:52:44 -0500 [thread overview]
Message-ID: <sjm1y1lyif7.fsf@kikki.mit.edu> (raw)
In-Reply-To: <20030305112852.GA22351@outpost.ds9a.nl>
bert hubert <ahu@ds9a.nl> writes:
> On Wed, Mar 05, 2003 at 12:29:12PM +0100, Andreas Jellinghaus wrote:
> > Hi,
> >
> > both manual keying and automatic keying with racoon (pre-shared secret)
> > are working fine. No need to patch or modify anything.
> > I tried only ipv4.
>
> By the way, regarding ipsec-tools 0.1, are you sure you want to fork the
> projects involved?
I spoke to the KAME people and unfortunately, at least for now, there
is no other choice but to fork. Perhaps down the road we can merge,
but as of last week they don't want to host a linux package. They are
willing to take some of our patches, but that doesn't help with a
build system.
> By the way, you did not mention it here but ipsec-tools is available on
> http://sourceforge.net/projects/ipsec-tools , I also link them from
> http://lartc.org/howto/lartc.ipsec.html
I didn't? Perhaps I said ipsec-tool.sourceforge.net which has a
link to sourceforge.net/projects/ipsec-tools and is much shorter
to type. ;)
> Regards,
>
> bert
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
warlord@MIT.EDU PGP key available
next prev parent reply other threads:[~2003-03-05 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1046863752.441.7.camel@simulacron>
2003-03-05 11:28 ` ipsec-tools 0.1 + kernel 2.5.64 bert hubert
2003-03-05 14:52 ` Derek Atkins [this message]
2003-03-05 21:28 ` Andreas Jellinghaus
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=sjm1y1lyif7.fsf@kikki.mit.edu \
--to=warlord@mit.edu \
--cc=ahu@ds9a.nl \
--cc=aj@dungeon.inka.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).