From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rymes To: development@lists.ipfire.org Subject: Apple IKEv2 and Ciphers Date: Sun, 06 Feb 2022 10:01:09 -0500 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0605605862059376466==" List-Id: --===============0605605862059376466== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable All, I wanted first to thank Michael for all the work put into creating the Apple = Configuration Profiles feature for IPSec. It=E2=80=99s really quite nice to u= se. Anyhow, I was surprised to find that the ciphers used included MODP_1024, whi= ch IPFire lists as =E2=80=9CBroken=E2=80=9D. Now, I=E2=80=99m the first to ad= mit that I do not fully grasp the intricacies of selecting a cipher suite, bu= t this seemed odd to me. I also noticed that the Profile is written to select= DH Group 21 (ECP_521), not MODP_1024, which is what ends up getting used. Using the default configuration profile from IPFire, this is what StrongSwan = Reports in the log: charon: 08[CFG] selected proposal: IKE:AES_GCM_16_256/PRF_HMAC_SHA2_256/MODP_= 1024=20 charon: 07[CFG] selected peer config =E2=80=98MyConnection'=20 charon: 07[CFG] selected proposal: ESP:AES_GCM_16_256/NO_EXT_SEQ=20 If I modify the Configuration Profile to use 256 bit AES-CBC, though, then EC= P_521ends up getting used.=20 charon: 05[CFG] selected proposal: IKE:AES_CBC_256/HMAC_SHA2_256_128/PRF_HMAC= _SHA2_256/ECP_521=20 Feb 6 09:50:09 stream charon: 13[CFG] selected peer config 'TomMacOS'=20 Feb 6 09:50:09 stream charon: 13[CFG] selected proposal: ESP:AES_GCM_16_256/= NO_EXT_SEQ=20 Is that an improvement, or does the elimination of GCM actually set things ba= ck? Tom --===============0605605862059376466==--