Bug 1315412 - ipsec.conf manpage does not contain any mention about crl-strict option
Summary: ipsec.conf manpage does not contain any mention about crl-strict option
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libreswan
Version: 7.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Paul Wouters
QA Contact: Jaroslav Aster
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-07 16:33 UTC by Jaroslav Aster
Modified: 2016-11-03 21:22 UTC (History)
0 users

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Cause: crl-strict option was backported without man page entry Consequence: no documentation of the feature was available in the ipsec.conf man page Fix: man page entry was also backported Result: crl-strict now appears in ipsec.conf man page
Clone Of:
: 1315415 (view as bug list)
Environment:
Last Closed: 2016-11-03 21:22:59 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2603 0 normal SHIPPED_LIVE Moderate: libreswan security and bug fix update 2016-11-03 12:13:02 UTC

Description Jaroslav Aster 2016-03-07 16:33:10 UTC
Description of problem:

Based on the bug 1265410, crl-strict option is new variant of option strictcrlpolicy, which is marked as obsolete, but ipsec.conf manpage does not contain any mention about crl-strict option. There is only strictcrlpolicy option in ipsec.conf manpage.

Version-Release number of selected component (if applicable):

libreswan-3.15-5.el7_1

How reproducible:

100%

Steps to Reproduce:

# man ipsec.conf | col -b | grep 'crl-strict'
# man ipsec.conf | col -b | grep 'strictcrlpolicy'

Actual results:

There is no mention about crl-strict option in ipsec.conf manpage.

Expected results:

There is mention about crl-strict option in ipsec.conf manpage and this option is main.

Additional info:

Comment 5 errata-xmlrpc 2016-11-03 21:22:59 UTC
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.

https://rhn.redhat.com/errata/RHSA-2016-2603.html


Note You need to log in before you can comment on or make changes to this bug.