Project

General

Profile

Bug #6263

Encryption options for every P2 on a given P1 are written to each P2 individually inside ipsec.conf with multiple P2 entries + split conn entries

Added by Jim Pingle 10 months ago. Updated about 1 month ago.

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
IPsec
Target version:
Start date:
04/25/2016
Due date:
% Done:

0%

Affected version:
All
Affected Architecture:

Description

When multiple Phase 2 entries exist, the encryption options for every P2 inside a given P1 are added to every split connection entries (IKEv1 or IKEv2 with split connections active)

For example, with three P2 entries all set for AES256-GCM-128, ipsec.conf has this in each conn entry:

    esp = aes256gcm128,aes256gcm128,aes256gcm128!

The same identical option is written on each connection.

If different options are used for P2s within the same tunnel, all of them are written to each P2. So each split conn entry contains all possible P2 algorithms for any P2 on the P1, not just the selected algorithm for that specific P2 entry.

History

#1 Updated by Chris Buechler 10 months ago

  • Target version changed from 2.3.1 to 2.3.2
  • Affected version changed from 2.3 to All

always been that way (well, w/strongswan, >=2.2.0). Doesn't hurt anything, not worth risking at this stage for 2.3.1.

#2 Updated by Chris Buechler 8 months ago

  • Target version changed from 2.3.2 to 2.4.0

#3 Updated by si lec 5 months ago

might be always been that way but this is very painful... all other brand do support this properly.
I just start using pfSense and this bug cause me quite a lot of trouble. You really need to fix this

#4 Updated by Jim Thompson about 1 month ago

  • Assignee set to Matthew Smith

Also available in: Atom PDF