Bug 1266093 - [RFE] Deprecate ssl_verify_depth config and use openssl defaults.
Summary: [RFE] Deprecate ssl_verify_depth config and use openssl defaults.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: subscription-manager
Version: 7.2
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: candlepin-bugs
QA Contact: John Sefler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-24 12:56 UTC by Adrian Likins
Modified: 2016-06-22 17:55 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-22 17:55:14 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Adrian Likins 2015-09-24 12:56:03 UTC
Description of problem:


We have a config option to set the X.509 server cert chain verify
depth to 3.

It was made configurable to address https://bugzilla.redhat.com/show_bug.cgi?id=649374
because it was explicitly set to '1' before that.

Why 3? (aside from 'thats what the current subscription.rhn.redhat.com cert needs to
get to redhat-uep.pem').

The openssl default seems to be 100 (https://www.openssl.org/docs/manmaster/ssl/SSL_CTX_set_verify.html)

My vote would be to let it fall to the openssl default by not explicitly setting it.
AFAICT, there is no utility to limiting the verify depth. 

Version-Release number of selected component (if applicable):
Pretty much all GA versions. But at least as new as: 
subscription-manager-1.16.2
python-rhsm-1.16.2




Additional info:

Comment 2 John Sefler 2015-09-25 17:17:03 UTC
deferring to rhel-7.3.0 due to schedule and severity


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