Bug 1583585 - [RFE] Revoke access from nodes using Certificate Revoke List in SSL
Summary: [RFE] Revoke access from nodes using Certificate Revoke List in SSL
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterfs
Version: unspecified
Hardware: Unspecified
OS: Linux
medium
low
Target Milestone: ---
: RHGS 3.5.0
Assignee: Mohit Agrawal
QA Contact: Vinayak Papnoi
URL:
Whiteboard:
Depends On: 1687326
Blocks: 1657798 1674379 1696806
TreeView+ depends on / blocked
 
Reported: 2018-05-29 10:09 UTC by Sonal
Modified: 2019-10-30 12:20 UTC (History)
12 users (show)

Fixed In Version: glusterfs-6.0-3
Doc Type: Enhancement
Doc Text:
Administrators can now prevent nodes with revoked certificates from accessing the cluster by adding a banned node's certificate to a Certificate Revocation List file, and specifying the file's path in the new ssl.crl-path volume option.
Clone Of:
: 1687326 (view as bug list)
Environment:
Last Closed: 2019-10-30 12:19:38 UTC
Embargoed:
mchangir: needinfo-

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:3249 0 None None None 2019-10-30 12:20:03 UTC

Comment 7 Sonal 2018-12-31 08:49:27 UTC 
Hi Vivek,

Could we have more information on if option ssl.crl-path is tested?

Regards,
Sonal Arora
Comment 14 Sachin P Mali 2019-02-01 10:24:27 UTC 
Hi Bipin,
This bug need through testing around SSL area not only respect to this bug. QE has to look for other areas around SSL. Because of that we have pushed this issue to next release.
We can plan to cover  all SSL related issues in one release.
Comment 15 Sachin P Mali 2019-02-01 18:16:49 UTC 
Hi Bipin, 
After analyzing this bug , we came to an agreement that QE will participate only in certificate revoke validation. Hence we are considering  this bug for BU4
Comment 42 Sunil Kumar Acharya 2019-05-13 07:07:28 UTC 
Restoring other needinfo
Comment 55 errata-xmlrpc 2019-10-30 12:19:38 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://access.redhat.com/errata/RHEA-2019:3249
Note You need to log in before you can comment on or make changes to this bug.