[issue37845] SLCertVerificationError: Unable to handle SAN names (from Certifications) published with white spaces at start

David K. added the comment: OK, I see your point :) Modification of the original certificiation is legally problematic. Much thanks for the patience and time to explain, D.K On Wed, Aug 14, 2019, 17:23 Christian Heimes wrote: > > Christian Heimes added the comment: > > On 14/08/2019

[issue37845] SLCertVerificationError: Unable to handle SAN names (from Certifications) published with white spaces at start

Christian Heimes added the comment: On 14/08/2019 15.37, David K. wrote: > > David K. added the comment: > > Hi, > > Judging by your comment, I think there is a an unfortnate misunderstanding. > > If you'd be kind enough, please let me explain: > > 1. The issue I had was indeed on Python

[issue37845] SLCertVerificationError: Unable to handle SAN names (from Certifications) published with white spaces at start

David K. added the comment: Hi, Judging by your comment, I think there is a an unfortnate misunderstanding. If you'd be kind enough, please let me explain: 1. The issue I had was indeed on Python 3.7, using the highly used "requests" library. Also my change was -not- applied on the

[issue37845] SLCertVerificationError: Unable to handle SAN names (from Certifications) published with white spaces at start

Christian Heimes added the comment: This is not a bug in Python but a misconfiguration on your side. A workaround for a misconfiguration doesn't belong into upstream code. The certificate validation code is security-sensitive and I don't feel comfortable to add unnecessary string

[issue37845] SLCertVerificationError: Unable to handle SAN names (from Certifications) published with white spaces at start

Change by David K. : -- keywords: +patch pull_requests: +14979 stage: -> patch review pull_request: https://github.com/python/cpython/pull/15260 ___ Python tracker ___

[issue37845] SLCertVerificationError: Unable to handle SAN names (from Certifications) published with white spaces at start

New submission from David K. : Unable to establish SSL connections using company's private certificates where their SANs (Subject Alternative Names) contain at least one DNS Name that starts with white spaces. Attempting to establish SSL connection would result in Exception: