1IPsec-tools 2=========== 3 4This package provides a way to use the native IPsec functionality 5in the Linux 2.6+ kernel. It works as well on NetBSD and FreeBSD. 6 7 - libipsec, a PF_KEYv2 library 8 - setkey, a tool to directly manipulate policies and SAs 9 - racoon, an IKEv1 keying daemon 10 11IPsec-tools were ported to Linux from the KAME project 12(http://www.kame.net) by Derek Atkins <derek@ihtfp.com>. 13 14Authors 15======= 16 17The ipsec-tools code has been maintained and developed by: 18 19 Emmanuel Dreyfus <manu@netbsd.org> 20 VANHULLEBUS Yvan <vanhu@free.fr> 21 Matthew Grooms <mgrooms@shrew.net> 22 Timo Teräs <timo.teras@iki.fi> 23 IHTFP Consulting <http://www.ihtfp.com/> 24 SUSE Linux AG <http://www.suse.com/> 25 26Under the NetBSD CVS repository, several other people maintain it. 27 28History 29======= 30 31Ipsec-tools was originally developed by the KAME project. It was then moved 32on SourfeForge, at the following address: 33 34 http://ipsec-tools.sourceforge.net/ 35 36Due to too restricted commit accesses, the development stalled, and the 37source code was moved into NetBSD's CVS repository, in: 38 39 src/crypto/dist/ipsec-tools 40 41However, many distributions still take their tarballs from SourceForge, and 42each distribution maintains local patches. 43 44FreeBSD maintains its own libipsec and setkey tools, in: 45 46 head/lib/libipsec/ 47 head/sbin/setkey/ 48 49A Trac used to exist, at the following address: 50 51 https://trac.ipsec-tools.net/ 52 53but the domain expired and was not renewed. 54 55The mailing lists from SourceForge still exist: 56 57 ipsec-tools-devel@lists.sourceforge.net 58 ipsec-tools-users@lists.sourceforge.net 59 60You can also browse the list archive: 61 http://sf.net/mailarchive/forum.php?forum_name=ipsec-tools-devel 62