You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Adrian Cole (JIRA)" <ji...@apache.org> on 2014/11/26 19:27:12 UTC

[jira] [Commented] (JCLOUDS-759) Make it easier to configure TLS overrides in apache hc driver

    [ https://issues.apache.org/jira/browse/JCLOUDS-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226577#comment-14226577 ] 

Adrian Cole commented on JCLOUDS-759:
-------------------------------------

I think we shouldn't address this. apache hc needs a rewrite or needs to be dropped regardless of this issue. It is *way* out of api parity with modern apachehc, and this will bite us sooner or later.

> Make it easier to configure TLS overrides in apache hc driver
> -------------------------------------------------------------
>
>                 Key: JCLOUDS-759
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-759
>             Project: jclouds
>          Issue Type: Sub-task
>          Components: jclouds-drivers
>    Affects Versions: 1.5.10, 1.6.3, 1.7.3, 1.8.1
>            Reporter: Adrian Cole
>            Priority: Minor
>             Fix For: 1.8.2
>
>
> The current apachehc driver is using all sorts of deprecated methods and also doesn't make it easy to allow the user to supply correct SSL configuration. Since it doesn't inherit the ssl config from the JVM, it needs to be explicitly specified.
> Let's change the default to not permit SSLv3 in a way that allows users to override that.
> Example is listed here.
> http://stackanswers.com/questions/26429751/java-http-clients-and-poodle



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)