[
https://issues.apache.org/jira/browse/JCLOUDS-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174446#comment-14174446
]
Andrew Phillips commented on JCLOUDS-753:
-----------------------------------------
> Users may be able to workaround by providing their own ExecutorServiceModule
> that has a
> custom SSLModule implementation within.
That's indeed a lot to ask. Were you able to have a look at the other drivers
to see whether they would avoid the problem?
> HttpCommandExecutorService(s) vulnerable to POODLE
> --------------------------------------------------
>
> Key: JCLOUDS-753
> URL: https://issues.apache.org/jira/browse/JCLOUDS-753
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
> Affects Versions: 1.7.3, 1.8.0
> Reporter: Diwaker Gupta
> Priority: Critical
> Fix For: 1.8.1
>
> Attachments: disable-sslv3.patch
>
>
> SSLModule configures the SSLContext thus:
> {noformat}
> sc = SSLContext.getInstance("SSL");
> sc.init(null, new TrustManager[] { trustAllCerts }, new
> SecureRandom());
> {noformat}
> This makes the client end of the SSL connection vulnerable to POODLE
> (http://googleonlinesecurity.blogspot.com/2014/10/this-poodle-bites-exploiting-ssl-30.html)
> jclouds should enforce TLS on all client connections.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
