-
-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ssl wildcat is not support #124
Comments
@bacnv Thank you for reporting the issue. I’ll check this as soon as I can and I’ll inform you what I found |
@bacnv I'll try to fix this issue tomorrow |
#140 is merged. The changes will be deployed on Sept. 30. If you have any issue with wildcard certs by using the latest master / newest package ( after sept. 30) please reopen this issue and ping me. |
@bacnv based on @srh's recognition (#140 (comment)) could you please provide a stack trace for me what is the Please note that I'll revert that change if the issue is on your side, because as Sam mentioned it should work, also I checked it again (I do not know what I checked in the past...) and it works. >>> cert = {'subject': ((('commonName', '*.example.co.uk'),),)}
>>> ssl.match_hostname(cert, "www.example.co.uk")
>>> |
Hi. Stumbled across this issue. Fwiw I think 2.4.4 actually broke things: 2.4.3
2.4.4
This is on:
|
Edit: This comment is all wrong because I read the version numbers wrong.
|
@srh @atomicules I had no time to validate this, but my guess is that #140 breaking the things with the wildcard thing what I did by "mistake". By mistake I mean it was a mistake to do that at all. Reverting that PR should solve the issue. What do you think @srh? I think that the Sorry for the noise @atomicules! |
Oh, my, I'm a moron. I read @atomicules's comment as 2.3.3 vs 2.3.4, so my previous post is all nonsense. |
I just arrived home and I'll be not able to do the release and revert. This will be my first thing tomorrow morning! I'm so sorry 😞 |
Revert PR : #150 |
@atomicules could you please try it now with |
Sure... it looks good to me:
Thanks! |
Describe the bug
I can't connect to RethinkDB using wildcat ssl
To Reproduce
Change hostname at match_hostname to wilcat and have a arg to check wildcat
Expected behavior
match_hostname(self._socket.getpeercert(), hostname="*."+(self.host.split('.', 1)[-1]))
Screenshots
System info
The text was updated successfully, but these errors were encountered: