You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "Ken Giusti (JIRA)" <ji...@apache.org> on 2012/12/14 20:26:12 UTC
[jira] [Assigned] (PROTON-161) SSL impl does not allow verification
of the peer's identity
[ https://issues.apache.org/jira/browse/PROTON-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ken Giusti reassigned PROTON-161:
---------------------------------
Assignee: Philip Harvey (was: Ken Giusti)
Just fixed this on the proton-c side. Needed a change to the API (configure the hostname string, and a new verify option in "set_verify").
Added new tests, which are skipped on Java.
Does proton-j already support this (hostname check in cert)? If so, we can just close this jira.
> SSL impl does not allow verification of the peer's identity
> -----------------------------------------------------------
>
> Key: PROTON-161
> URL: https://issues.apache.org/jira/browse/PROTON-161
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-j
> Affects Versions: 0.3
> Reporter: Ken Giusti
> Assignee: Philip Harvey
> Priority: Blocker
>
> The current SSL implementation validates the peer's certificate, and will not permit the connection to come up if the certificate is invalid.
> However - it does not provide a way to check if the peer's identity as provided in the certificate is the expected identity (eg, the same hostname used to set up the TCP connection). While a certificate may be valid (that is, signed by a CA trusted by the client), it may not belong to the intended destination.
> RFC2818 explains how this should be done - see section 3.1 Server Identity.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira