Bug 1743649
Summary: | ipsec auto --listall prints un-escaped left/right ID | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Jaroslav Aster <jaster> |
Component: | libreswan | Assignee: | Paul Wouters <pwouters> |
Status: | CLOSED ERRATA | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 8.0 | CC: | dapospis, hugh, omoris, pvrabec, pwouters |
Target Milestone: | rc | Keywords: | Triaged |
Target Release: | 8.0 | Flags: | pm-rhel:
mirror+
|
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-11-04 03:18:00 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1820206 | ||
Bug Blocks: |
Description
Jaroslav Aster
2019-08-20 11:36:33 UTC
"escaping" was introduced as a fix to bz 868986 It allows "," and "/" to be used within the ASCII representation of an OID even though they normally are separators. I have no idea if this follows some standard. commit 542f32f1f1c9a8dfce850271eeea445ac3653e75 was intended to do the reverse. The result is any ASCII representation produced by libreswan could be used as an input to libreswan. The representation in /etc/ipsec.conf looks like the representation in the output of --listall (i.e. with escapes). This seems like a Good Thing. In what way is this a problem? Jaroslav, I still do not fully understand the bug. The ID input specifies 2 comma's, did you expect 4 in the print? What is on the certificate / ASN itself ?Can you show the output of: openssl x509 -in file.crt -nooout -subject This has been addressed upstream where this handling has been improved. It did change a lot of string functions, so this cannot be reasonably backported. It will come into RHEL via a rebase to 3.30 Hi Paul, do you still need my answer or, based on the comment #3, you understand where is the issue? Allowing the old ,, syntax support was added upstream. Will be part of 3.32 release. Upstream test case is ikev2-x509-39-OU-comma 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 (libreswan bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2020:4722 |