[
https://issues.apache.org/jira/browse/MTOMCAT-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15868382#comment-15868382
]
Cory Lum commented on MTOMCAT-309:
----------------------------------
Just want to note that this is an issue when using JDK 1.7. I believe JDK 1.8
already removed the risky protocols.
> Allow specifying sslProtocols via pom configuration
> ---------------------------------------------------
>
> Key: MTOMCAT-309
> URL: https://issues.apache.org/jira/browse/MTOMCAT-309
> Project: Apache Tomcat Maven Plugin
> Issue Type: Bug
> Components: tomcat7
> Affects Versions: 2.2
> Reporter: Cory Lum
> Assignee: Olivier Lamy (*$^¨%`£)
> Labels: easyfix
>
> There is currently no way to specify the sslProtocol. The only workaround is
> to use a custom server.xml.
> The httpsConnector is hardcoded to use TLS.
> httpsConnector.setProperty( "sslProtocol", "TLS" );
> Due to security reasons, this version is insufficient for many modern browser
> (chrome and firefox) without having to manually compromise the browser's
> security settings which expects communication via TLSv1.2
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
