[Openswan dev] openswan 2.1.0rc1 rpms
mcr at sandelman.ottawa.on.ca
Wed Mar 10 09:48:00 CET 2004
-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "Axel" == Axel Thimm <Axel.Thimm at ATrpms.net> writes:
>> That would include: 1) all 2.6 kernels. (maybe not 2.6.0?) 2)
>> 2.4 with back-ported 26sec 3) any kernel source tree that has
>> ( cd openswan-X.Y.Z && make nattpatch ) | (cd /usr/src/linux &&
>> patch -p1) done to it prior to a *complete* build.
Axel> OK, I had (mistakenly) assumed this patch was already in the
No, it is not, because if it was, it would break when applied to any
kernel that had the NAT-T patch already there.
We should be releasing a second patch set, but since it will rarely
change, it might be matter much.
Axel> There is interest in getting older RH flavours (from FC1 down
Axel> to RH7.3) running with NAT-T. For ATrpms it is probably easier
Axel> to have the kernels patched. If people from other
The problem is that one then has to answer support questions for users
that would otherwise have gone to RH.
Axel> distributions are interested in supporting NAT-T in 2.4, and
Axel> don't want to rebuild kernels (because they would have to
Axel> rebuild vendor kernel modules), such a module could be useful,
Axel> but I don't really think the demnd is that high. Better invest
Axel> the time on other areas. :)
Yes, I agree.
Axel> I'll try to get patched kernels until the next weekend. --
] ON HUMILITY: to err is human. To moo, bovine. | firewalls [
] Michael Richardson, Xelerance Corporation, Ottawa, ON |net architect[
] mcr at xelerance.com http://www.sandelman.ottawa.on.ca/mcr/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys
-----END PGP SIGNATURE-----
More information about the Dev