Project

General

Profile

Actions

Bug #12323

closed

IPsec Phase 2 entry incorrectly orders proposals in AH mode

Added by Viktor Gurov 9 months ago. Updated 7 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
IPsec
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
22.01
Release Notes:
Default
Affected Version:
2.5.2
Affected Architecture:

Description

If you select all hashing algorithms in AH mode, it sets the MD5 cipher to the first place of ah_proposals:

ah_proposals = md5-modp2048,sha1-modp2048,sha256-modp2048,sha384-modp2048,sha512-modp2048,aesxcbc-modp2048

correct order should be:

ah_proposals = sha512-modp2048,sha384-modp2048,sha256-modp2048,sha1-modp2048,aesxcbc-modp2048,md5-modp2048

similar to #11078

Actions #2

Updated by Jim Pingle 9 months ago

  • Status changed from New to Pull Request Review
  • Assignee set to Viktor Gurov
  • Target version set to 2.6.0
  • Plus Target Version set to 21.09
Actions #3

Updated by Viktor Gurov 9 months ago

  • Status changed from Pull Request Review to Feedback

Merged

Actions #4

Updated by Jim Pingle 8 months ago

  • Subject changed from IPsec PH2 incorrect proposals order in AH mode to IPsec Phase 2 entry incorrectly orders proposals in AH mode

Updating subject for release notes.

Actions #5

Updated by Alhusein Zawi 8 months ago

order seems ok

ah_proposals = sha512-modp2048,sha384-modp2048,sha256-modp2048,sha1-modp2048,md5-modp2048,aesxcbc-modp2048

2.6.0.a.20210910.0100

Actions #6

Updated by Jim Pingle 8 months ago

  • Status changed from Feedback to Resolved
Actions #7

Updated by Jim Pingle 7 months ago

  • Plus Target Version changed from 21.09 to 22.01
Actions

Also available in: Atom PDF