Description of problem:
During the Openswan code review for CCC evaluation, there are 2 issues found upto now:
1. Labeled-ipsec code changes cause call to add_pending() in the function ikev2parent_outI1() in the file program/pluto/ikev2_parents.c to be out of HAS_IPSEC_POLICY(policy) check something unintended in the original code.
2. Very large security label strings received from the peer should not be truncated and should return false immediately leading to connection termination.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. code review.
The above stuff happens in the code.
The above stuff should not happen in the code.
I think that I am not sure how to test the above thing except from a code review again.
The version is openswan-2.6.32-4.el6.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Prior to this update, very large security label strings received from the peer were being truncated. The truncated string was then still used. However, this truncated string could, under rare circumstances, turn out to be a valid string, leading to an incorrect policy. Additionally, erroneous queuing of on-demand requests of setting up an IPsec connection was discovered in the IKEv2 (Internet Key Exchange) code. Although not harmful, it was not the intended design. This update fixes both of these issues, and Openswan now correctly handles the IKE setup.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.