You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Emmanuel Lécharny (Jira)" <ji...@apache.org> on 2020/04/20 14:09:00 UTC
[jira] [Comment Edited] (DIRMINA-1122) Add support for endpoint
identification algorithm
[ https://issues.apache.org/jira/browse/DIRMINA-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17087766#comment-17087766 ]
Emmanuel Lécharny edited comment on DIRMINA-1122 at 4/20/20, 2:08 PM:
----------------------------------------------------------------------
I believe this can be done through your own implementation of a TrustManager that you inject in the SSLContext instance.
was (Author: elecharny):
I believe this can be done through your own implementation of a TrsutManager that you inject in the SSLContext instance.
> Add support for endpoint identification algorithm
> -------------------------------------------------
>
> Key: DIRMINA-1122
> URL: https://issues.apache.org/jira/browse/DIRMINA-1122
> Project: MINA
> Issue Type: Improvement
> Components: Filter, SSL
> Affects Versions: 2.0.22, 2.1.3
> Reporter: Marcin L
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Support for endpoint identification algorithm was added in Java 1.7. Currently MINA supports providing single SNI name via org.apache.mina.filter.ssl.SslFilter#PEER_ADDRESS session attribute, but there is no way verifying it matches the certificate received.
> It would be nice if we could provide endpoint identification algorithm to SslFilter so certificate's common name or subject alternative names are verified.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@mina.apache.org
For additional commands, e-mail: dev-help@mina.apache.org