[
https://issues.apache.org/jira/browse/THRIFT-3599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15138410#comment-15138410
]
Hudson commented on THRIFT-3599:
--------------------------------
SUCCESS: Integrated in Thrift-precommit #45 (See
[https://builds.apache.org/job/Thrift-precommit/45/])
THRIFT-3599 Validate client IP address against cert's SubjectAltName (nsuke:
[https://github.com/apache/thrift/commit/f39f7dbd26fe090f0fc6566c100ca7adc9ace714])
* lib/py/src/transport/TSSLSocket.py
* lib/py/test/test_sslsocket.py
* test/keys/README.md
* test/keys/client_v3.key
* test/keys/client_v3.crt
> Validate client IP address against cert's SubjectAltName
> --------------------------------------------------------
>
> Key: THRIFT-3599
> URL: https://issues.apache.org/jira/browse/THRIFT-3599
> Project: Thrift
> Issue Type: Bug
> Components: Python - Library
> Reporter: Aki Sukegawa
> Assignee: Aki Sukegawa
> Priority: Critical
> Fix For: 0.9.4
>
>
> After THRIFT-3505, python TSSLSocket has client cert support but does not
> perform any hostname matching.
> That means clients can submit any certificate that is unrelated to them and
> the server side only check if the cert is in their CA.
> It is in a sense worse than nothing as it can introduce false sense of
> security.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
