[strongSwan] Augment the "esp cipher suites" with foreign not standard ciphers
martin at strongswan.org
Fri Oct 8 11:20:52 CEST 2010
> The IP data flow is not IPsec-ed by Linux but by an external NPU.
I see. I assume you're using our PF_KEY kernel interface plugin, then.
> Then, probably only the items 3) and 4) from your list are required.
You'll need 5), too. Your NPU probably provides a PF_KEY algorithm
identifier (such as SADB_X_EALG_XY) for your cipher. You'll have to map
the IKEv2 specific identifier to the PF_KEY identifier in .
> Concerning the item 3, if we choose an IKEv2 algorithm identifier
> then how we can specify it with strongSwan?
IKEv2 algorithm identifiers for ciphers are defined at . Above 1024
are private use identifiers not managed by IANA.
> what should be done for the item 4 ("proposal configuration option").
Sets of algorithm identifiers are encoded into proposals, these are used
the negotiate an algorithm set to use. The proposals are attached to
configurations and must be configured. Without your algorithm in the
proposal, you won't have a chance to negotiate it with your peer.
To configure a connection with a proposal using your algorithm
identifier via the ipsec.conf esp= option, you'll need a keyword.
These keywords are defined in  and mapped to your defined identifier.
> A simple but not elegant solution is to negotiate a well-known/supported
> Cipher but, by convention, to apply to the both ends of the tunnel the
> new cipher (not related to negotiated one).
Is the simplest option, but might be very confusing. Using private use
identifiers is the clean way. strongSwan currently requires the
strongSwan vendor ID for private use identifiers, as an other
implementation might use a different algorithm for the same private use
More information about the Users