Attachment 863088 Details for Bug 1018327 – replacement phase2alg.xml

replacement phase2alg.xml

phase2alg.xml (text/xml), 1.52 KB, created by Paul Wouters on 2014-02-14 04:15:40 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Paul Wouters

Created: 2014-02-14 04:15:40 UTC

Size: 1.52 KB

patch

obsolete

>  <varlistentry>
>  <term><emphasis remap='B'>phase2alg</emphasis></term>
>  <listitem>
><para> Specifies the algorithms that will be offered/accepted for a phase2
>negotiation. If not specified, a secure set of defaults will be used. Sets
>are separated using comma's.
></para>
><para>The default values are the same as for ike=
>Note also that not all ciphers available to the kernel (eg through CryptoAPI)
>are necessarilly supported here.</para>
><para> The format for ESP is ENC-AUTH followed by an optional PFSgroup. For
>instance, "3des-md5" or "aes256-sha1;modp2048" or  "aes-sha1,aes-md5".
></para>
><para>For RFC-5114 DH groups, use the "dh" keyword, eg "aes256-sha1;dh23"
></para>
><para> The format for AH is AUTH followed by an optional PFSgroup. For
>instance, "md5" or "sha1;modp1536".
></para>
><para>AES-GCM and AES-CCM use the syntax like
>"phase2alg=aes_ccm_c-256-null". The only supported key sizes are 128,
>192 and 256. The subscript (_a, _b and _c) stand for the ICV versions
>(8,12,16). It is recommended to migrate to the _c versions, as support
>for smaller ICV's will be removed in the future.</para>
><para>Note that openswan and versions of libreswan up to 3.6 require
>adding the salt size to the key size. Therefor, to interop with an older
>version of openswan or libreswan, use: "phase2alg=aes_ccm_c-280-null". For
>CCM, the 'keysize' needs to be increased by 24, resulted in valid keysizes
>of 152, 215 and 280. For GCM the 'keysize' needs to be increased by 32,
>resulting valid 'keysizes' of 160, 224 and 288.
></para>
>  </listitem>
>  </varlistentry>

Actions: View

Attachments on bug 1018327: 863088