[Openswan dev] [openswan dev] from ipsec.conf to internal representation

Paul Wouters paul at xelerance.com
Mon Jun 25 13:04:50 EDT 2007

On Mon, 25 Jun 2007, mds wrote:

> Hello everybody.
> I'm currently trying to implement Multi-Layer IPsec based on
> the Openswan 2.4.7 source code.
> The goal is to be able to en-/decrypt the TCP header in the
> IP datagrams using an additional key. Hence I would like to
> add an additional key to the ipsec.conf file and have it parsed
> and transfered to the internal representation of the connection
> data.
> This is my view on how the keys are processed:
> starter.c: main(...) calls confread.c confread_load(...)

You should use openswan 2.5.x as code base, since it has a completely
redesigned "starter" code build in as libipsecconf.

Building and integrating Virtual Private Networks with Openswan:

More information about the Dev mailing list