Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1360134 - libreswan needs to check additional CRLs after LDAP CRL distributionpoint fails
Summary: libreswan needs to check additional CRLs after LDAP CRL distributionpoint fails
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libreswan
Version: 6.7
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: ---
Assignee: Paul Wouters
QA Contact: Jaroslav Aster
URL:
Whiteboard:
Depends On:
Blocks: 1416143 1416144
TreeView+ depends on / blocked
 
Reported: 2016-07-26 06:02 UTC by Karel Srot
Modified: 2017-03-21 09:06 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1347735
: 1416143 (view as bug list)
Environment:
Last Closed: 2017-03-21 09:06:27 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0575 normal SHIPPED_LIVE libreswan bug fix update 2017-03-21 12:23:23 UTC

Description Karel Srot 2016-07-26 06:02:14 UTC
The fix was requested to be backported to 6.9 too.

+++ This bug was initially created as a clone of Bug #1347735 +++

Description of problem:

When multiple CRL distributionpoints are present in a certificate, and the ldap URI fails, libreswan does not attempt another URI like http.

I believe LDAP is always attempted first?

This is related to a missing feature in NSS:

https://bugzilla.mozilla.org/show_bug.cgi?id=1280276

Comment 20 errata-xmlrpc 2017-03-21 09:06:27 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/RHBA-2017-0575.html


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