Charon-Pluto IKEv1 Interoperability » History » Version 8
Charon-Pluto IKEv1 Interoperability¶
- IKEv1 Interoperability Test Cases between the strongSwan Charon and Pluto daemons.
Migration from Pluto to Charon¶
We've tried hard to support most of pluto configurations in charon. But please keep in mind that IKEv1 in charon is a completely new implementation and that it might behave different than IKEv1 in pluto.
NAT-Traversal is always enabled in charon, for both IKEv1 and IKEv2. The IKEv2 eap keywords has been removed.
Deprecated, but still supported keywords¶
The authby and xauth keywords are still supported, but deprecated. Please migrate your installation to the leftauth / rightauth keywords. XAuth is configured as multiple rounds using leftauth2 / rightauth2 keywords (i.e. leftauth=pubkey, leftauth2_=xauth). To configure the new Hybrid Mode, define _leftauth=xauth and rightauth=pubkey.
Perfect Forward Secrecy (PFS)¶
The pfs option has been removed. IKEv1 now uses the same syntax to define PFS as we use it in IKEv2. To enable PFS, include the Diffie-Hellman group in your ESP proposal, esp=aes128-sha1-modp2048.
Smartcards and PKCS#11¶
IKEv1 can use the same PKCS#11 backend as IKEv2, all pluto specific PKCS#11 options are obsolete.
Narrowing with rightsubnetwithin¶
The IKEv1 responder narrowing keyword rightsubnetwithin is not supported anymore. Instead, the leftsubnet / rightsubnet definitions are automatically narrowed if required. Please be aware that IKEv1 does actually not support narrowing, and returning a smaller subnet than requested might confuse the initiator (but works fine with charon). To interoperate with other implementations, make sure your subnet definitions match exactly.