Mitsuru KANDA wrote:
>Hello Linux kernel network maintainers,
>
>I'm a member of USAGI project.
>
>In IPv6 specifications, IPsec is mandatory.
>
>We implemented IPsec for Linux IP stack.
>
>At present, our implementation includes:
> PF_KEY V2 interface,
> Security Association Database and
> Security Policy Database for whole IP versions,
> IPsec for IPv6,(transport, tunnel mode),
> IPsec for IPv4 (transport mode),
>
>Would you mind checking it ?
>
Is this code being checked in to the mainline kernel? Or becoming part
of the
CryptoAPI patch set? Bravo, in either case.
How does that affect FreeS/WAN development?
>
>
> Is this code being checked in to the mainline kernel? Or becoming part
> of the
> CryptoAPI patch set? Bravo, in either case.
We will be incorporating lots of ideas and small code pieces
from USAGI's work, but most of the core engine will be a new
implementation.
A completely new CryptoAPI subsystem has been implemented so that
full lists of page vectors can be passed into the ciphers, which is
necessary for a clean IPSEC implementation.
It is intended that this work will be complete (it isn't done as I
type this) and pushed to Linus upon his return from vacation.
In article <[email protected]> (at 20 Oct 2002 19:41:06 -0700), "David S. Miller" <[email protected]> says:
> > Is this code being checked in to the mainline kernel? Or becoming part
> > of the
> > CryptoAPI patch set? Bravo, in either case.
>
> We will be incorporating lots of ideas and small code pieces
> from USAGI's work, but most of the core engine will be a new
> implementation.
:
> It is intended that this work will be complete (it isn't done as I
> type this) and pushed to Linus upon his return from vacation.
Well, we'd like to learn more about your ideas...
Source code is our friend.
If you don't mind, would you send "as-is" codes to us?
--
Hideaki YOSHIFUJI @ USAGI Project <[email protected]>
GPG FP: 9022 65EB 1ECF 3AD1 0BDF 80D8 4807 F894 E062 0EEA
It is all bolted togather and does not need to be piece from random parts.
Thus in simple reality, it is superior.
Maybe FreeS/WAN will get busy and compete or die.
Cheers,
Andre Hedrick
LAD Storage Consulting Group
On Mon, 21 Oct 2002, Sandy Harris wrote:
> Mitsuru KANDA wrote:
>
> >Hello Linux kernel network maintainers,
> >
> >I'm a member of USAGI project.
> >
> >In IPv6 specifications, IPsec is mandatory.
> >
> >We implemented IPsec for Linux IP stack.
> >
> >At present, our implementation includes:
> > PF_KEY V2 interface,
> > Security Association Database and
> > Security Policy Database for whole IP versions,
> > IPsec for IPv6,(transport, tunnel mode),
> > IPsec for IPv4 (transport mode),
> >
> >Would you mind checking it ?
> >
> Is this code being checked in to the mainline kernel? Or becoming part
> of the
> CryptoAPI patch set? Bravo, in either case.
>
> How does that affect FreeS/WAN development?
>
> >
> >
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
On Mon, 2002-10-21 at 04:41, David S. Miller wrote:
> A completely new CryptoAPI subsystem has been implemented so that
> full lists of page vectors can be passed into the ciphers, which is
> necessary for a clean IPSEC implementation.
oh... nice to learn about your plans (so late) at all ;-)
well, it would be cool if you'd cooperate (or at least share
information) with us (the official cryptoapi project ;-), as we're open
for the design requirements of the next generation cryptoapi...
...otherwise this may render the kerneli.org/cryptoapi effort completely
useless :-/ ...of course, if it's your long term goal to take the
cryptoapi development away from kerneli.org, I'd like to know too ;-)
regards,
--
Herbert Valerio Riedel / Phone: (EUROPE) +43-1-58801-18840
Email: [email protected] / Finger [email protected] for GnuPG Public Key
GnuPG Key Fingerprint: 7BB9 2D6C D485 CE64 4748 5F65 4981 E064 883F
4142