Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
..
Failed to load latest commit information.
patches
po
source
README.Debian
README.source
changelog
compat
control
copyright
ipsec.secrets.proto
logcheck.ignore.paranoid
logcheck.ignore.server
logcheck.violations.ignore
openswan-dbg.links
openswan-doc.doc-base
openswan-doc.docs
openswan-doc.lintian-overrides
openswan-modules-dkms.dirs
openswan-modules-dkms.dkms.conf.in
openswan-modules-dkms.docs
openswan-modules-dkms.lintian-overrides
openswan-modules-dkms.postinst
openswan-modules-dkms.prerm
openswan-modules-source.control.in
openswan-modules-source.dirs
openswan-modules-source.docs
openswan-modules-source.kernel-config
openswan-modules-source.lintian-overrides
openswan-modules-source.lintian-overrides.in
openswan-modules-source.rules
openswan.config
openswan.dirs
openswan.docs
openswan.lintian-overrides
openswan.postinst
openswan.postrm
openswan.preinst
openswan.prerm
openswan.templates
rules
source.lintian-overrides

README.Debian

  This package is NOT an official Debian package from the Debian openswan
  maintainers.

openswan for Debian
----------------------

1) General Remarks

This package has been created from scratch with some ideas from the
freeswan 1.3 package by Tommi Virtanen and the freeswan 1.5 package by
Aaron Johnson merged in. Most of the (already removed) code in debian/rules
for creating the linux-patch-openswan package was initially taken from Tommi
Virtanen's package, but had been mostly rewritten to fit the needs of different
kernel versions (since version 1.9-1).

After the decision of the FreeS/WAN project to cease the development of
FreeS/WAN, the Debian package team decided to switch over to the Openswan fork.
This code base included all the patches that had to be applied manually before,
which made packaging simple. Alexander List prepared the first preliminary
openswan package based on Rene Mayrhofer's freeswan packaging, who in turn
updated to the relevant parts of the last freeswan package.

2) Plain RSA key creation

Note: Usage of such keys is deprecated in favour of newer X.509 certificates.

If you still want to create an old style plain RSA key, you can create it with
    ipsec rsasigkey $KEYLENGTH > $TMPFILE
where $KEYLENGTH should be >= 2048. The resulting private key must be inserted
into /etc/ipsec.secrets and enclosed with a ": RSA { .... }" marker. The
following commands can be used to create a correctly formatted block:
    echo -e ': RSA\t{' >> /etc/ipsec.secrets; 
    cat $TMPFILE >> /etc/ipsec.secrets; 
    echo -e '\t}' >> /etc/ipsec.secrets;
Afterwards, it is recommended to remove $TMPFILE in a secure manner (using
something line srm, shred, wipe...) and create a public key line for insertation
into the "conn" section of ipsec.conf with 
    ipsec showhostkey --left 
(or "--right" depending on which side you want to use it). For further
information please take a closer look at the manpages ipsec_rsasigkey,
ipsec.secrets, ipsec_showhostkey and ipsec.conf.

3) IPsec Kernel Support

Note: This package per default uses the in-kernel IPsec stack, which is 
available in all recent stock Debian kernel images. The advantage of this
in-kernel stack is that it is well supported and does not require external
modules to be built. The disadvantage is that it no longer uses virtual ipsecX
network interfaces and therefore makes debugging IPsec connections slightly
harder (e.g., tcpdump can not be used separately on encrypted and unencrypted
traffic).

If you want to use the openswan utilities, you will need the appropriate
kernel modules. The Debian default kernel native IPsec stack can be used
out-of-the-box with openswan pluto, the key management daemon. This native Linux
IPsec stack is of high quality, has all of the features of the latest Debian
freeswan and openswan packages (i.e. support for other ciphers like AES and NAT
Traversal support) and is well integrated into the kernel networking subsystem
(which is not true for the openswan kernel modules). The easiest way to get
IPsec support in Debian is to use the default kernels (or recompile from the
Debian kernel sources).

If you do not want to use the in-kernel IPsec stack, then the openswan kernel
part can be compiled as stand-alone module. Starting with kernel >= 2.6.23 and
openswan >= 2.6.22, NAT Traversal will work without patching the kernel, also
with KLIPS compiled as a module. Therefore, the linux-patch-openswan package and
the NAT Traversal patches have both been dropped. On the other hand, please note
that there are two packages available, each gearing towards a different group
of users:

* openswan-modules-dkms is suitable for end users to use KLIPS on the same 
  machine where the package is being installed. The module will be built 
  automatically upon installing a new kernel and its respective headers 
  package. No further documentation is necessary, as the build and installation
  process is fully automatic when this package and the kernel headers are 
  installed.

* openswan-modules-source targets the system administrators wishing to 
  distribute pre-built KLIPS modules to multiple machines as a standard Debian 
  package. This approach takes more work but is also a lot more flexible.

4) Building KLIPS from openswan-modules-source

For building modules with openswan-modules-source three different approaches
can be used:

* The easiest way consists of installing module-assistant and the needed
  linux-headers packages, then simply issuing
      module-assistant build openswan
  to build the package.
  Please note that when compiling modules for a kernel version which differs
  from the one running on the compilation host then the option --kvers-list 
  must be supplied to the module-assistant command.

* When invoking make-kpkg from kernel-package to do the module compilation the
  linux-source package has to be installed and the openswan-modules.tar.gz
  from openswan-modules-source needs to be extracted under /usr/src. Keep in
  mind that it is not enough to just put the linux source tree in place,
  but it also needs to be configured and a successful kernel build process
  must be completed before the command
      make-kpkg --added_modules openswan modules_image
  can be used to actually compile and package the module.
  Note that, in order to work with a specific kernel version, it's likely that
  also the options --append_to_version and --revision will need to be set. For
  getting example values of the running kernel, issue the command
      uname -r | sed 's/.*\.[0-9]*-/-/'
  to retrieve the --append_to_version parameter and look at the Version column
  in the output of the line
      dpkg --list linux-image-`uname -r`
  which provides the --revision argument.

* Invoking debian/rules directly is the third and most flexible approach to
  compile and package the module, but this method also leaves the task of 
  cleaning up to the administrator. After extracting openswan-modules.tar.gz 
  change to /usr/src/modules/openswan and issue the command
      debian/rules binary-modules
  to start building the module. Some variables that might need to be set in
  order to make the process run correctly:
      KVERS: the complete kernel version (as retrieved by 'uname -r')
      KDREV: the kernel revision (equal --revision argument)
      KSRC: the location of the kernel tree (/usr/src/linux-headers-`uname -r`
                                             for example)
      KMAINT: the binary package maintainer (defaults to Rene Mayrhofer)
      KEMAIL: the maintainer's mailaddress (defaults to rmayr@debian.org)
  Please remember to clean up completely after building the binary package by
  calling
      debian/rules kdist_clean
  Otherwise, future build processes might lead to incorrect results.

5) Using Openswan with SAref

In order to use the SAref feature allowing users to connect multiple clients
from behind the same NAT device and multiple clients using the same internal IP
behind different NAT devices, the Linux kernel needs to be patched. At the time
of this writing there are patches available for kernel version 2.6.32 from 
Lenny/Sid and 2.6.35-rc6 from experimental which are shipped in the
openswan-modules.tar.bz2 file from openswan-modules-source.
The recommended method for creating a patched kernel is using the make-kpkg
approach which is documented in the above section. After extracting the linux
and the openswan source in /usr/src change to the to the kernel source
directory and patch the source code by issuing the commands
    patch -p1 < /usr/src/modules/openswan/patches/kernel/$VERSION/0001-SAREF-add-support-for-SA-selection-through-sendmsg.patch
    patch -p1 < /usr/src/modules/openswan/patches/kernel/$VERSION/0002-SAREF-implement-IP_IPSEC_BINDREF.patch
where $VERSION is the base kernel version (without the --append_to_version
suffix). To enable the new feature in the kernel config, compile the kernel
and the openswan module, you may also want to install libncurses5-dev and then
call make-kpkg this way:
    make-kpkg --append_to_version APPEND_PARAM --revision REVISION_PARAM \
    --added_modules openswan --initrd --config menuconfig configure kernel_\
    image modules_image
In the displayed menu first enter "Networking support", then proceed to
"Networking options", there select "IP: IPsec SAref interface (KLIPS)". When
exiting answer yes to save your new kernel configuration so that make-kpkg
uses it when compiling the new kernel. Afterwards install the newly created
linux-image and openswan-modules packages and then reboot the computer.
To finally activate the SAref feature the ipsec.conf file must be modified: In
the config setup section protostack=mast has to be specified and overlapip=yes
needs to be added to the affected conn descriptions. Also note that the MAST
stack does not use "eroutes", so the
    ipsec eroute
command no longer returns tunnel information, at the moment please issue
    ipsec auto --status
to retrieve connection details.