[jira] [Commented] (JCLOUDS-753) HttpCommandExecutorService(s) vulnerable to POODLE

[ https://issues.apache.org/jira/browse/JCLOUDS-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174455#comment-14174455 ] Diwaker Gupta commented on JCLOUDS-753: --- [~andrewp] yes, see Ignasi's comment earli

[jira] [Commented] (JCLOUDS-753) HttpCommandExecutorService(s) vulnerable to POODLE

[ https://issues.apache.org/jira/browse/JCLOUDS-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174271#comment-14174271 ] Diwaker Gupta commented on JCLOUDS-753: --- [~andrewp] we did explore that possibility

[jira] [Updated] (JCLOUDS-753) HttpCommandExecutorService(s) vulnerable to POODLE

[ https://issues.apache.org/jira/browse/JCLOUDS-753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diwaker Gupta updated JCLOUDS-753: -- Attachment: disable-sslv3.patch Attached patch seems to work, but should be independently teste

[jira] [Updated] (JCLOUDS-753) HttpCommandExecutorService(s) vulnerable to POODLE

[ https://issues.apache.org/jira/browse/JCLOUDS-753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diwaker Gupta updated JCLOUDS-753: -- Priority: Critical (was: Major) Affects Version/s: 1.7.3 Fix Version/s: 1.

[jira] [Commented] (JCLOUDS-753) HttpCommandExecutorService(s) vulnerable to POODLE

[ https://issues.apache.org/jira/browse/JCLOUDS-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174209#comment-14174209 ] Diwaker Gupta commented on JCLOUDS-753: --- [~nacx] [~andrewp] indeed both OkHttp and

[jira] [Commented] (JCLOUDS-753) HttpCommandExecutorService(s) vulnerable to POODLE

[ https://issues.apache.org/jira/browse/JCLOUDS-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172901#comment-14172901 ] Diwaker Gupta commented on JCLOUDS-753: --- I should note that `getInstance("TLS")` or

[jira] [Created] (JCLOUDS-753) HttpCommandExecutorService(s) vulnerable to POODLE

Diwaker Gupta created JCLOUDS-753: - Summary: HttpCommandExecutorService(s) vulnerable to POODLE Key: JCLOUDS-753 URL: https://issues.apache.org/jira/browse/JCLOUDS-753 Project: jclouds Issue

[jira] [Commented] (JCLOUDS-480) support AWS signature version 4 for S3

[ https://issues.apache.org/jira/browse/JCLOUDS-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118919#comment-14118919 ] Diwaker Gupta commented on JCLOUDS-480: --- Thanks [~gaul]. As you note, most S3 clone

[jira] [Commented] (JCLOUDS-645) Incorrect endpoint url chosen for default region of HPCloud Object Storage

[ https://issues.apache.org/jira/browse/JCLOUDS-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14084897#comment-14084897 ] Diwaker Gupta commented on JCLOUDS-645: --- [~ccustine] wrote: > My question is whethe

[jira] [Commented] (JCLOUDS-589) Port fix for JCLOUDS-178 to non-keystone-v2.0 auth implementations

[ https://issues.apache.org/jira/browse/JCLOUDS-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14036664#comment-14036664 ] Diwaker Gupta commented on JCLOUDS-589: --- Folks, the PR seems ready (https://github.

[jira] [Commented] (JCLOUDS-432) Revert Guava/7u51 incompatibility workaround as soon as Guava 1635 is fixed

[ https://issues.apache.org/jira/browse/JCLOUDS-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13891034#comment-13891034 ] Diwaker Gupta commented on JCLOUDS-432: --- Guava 16.0.1 released with a fix for issue