[
https://jira.codehaus.org/browse/WAGON-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318414#comment-318414
]
Olivier Lamy commented on WAGON-383:
------------------------------------
bin.zip or bin.tar.gz available for testing here
https://builds.apache.org/view/M-R/view/Maven/job/maven-3.x/
> Regression for SSLv3
> --------------------
>
> Key: WAGON-383
> URL: https://jira.codehaus.org/browse/WAGON-383
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http
> Affects Versions: 2.2, 2.3
> Environment: Operation system independent, but tested on Macbook Pro
> with 10.6 and Red Hat Enterprise Linux 6 on a virtual machine.
> Reporter: James Kionka
> Priority: Critical
> Fix For: 2.4
>
>
> When attempting to access a Maven repository which uses SSLv3, you get the
> following error, "javax.net.ssl.SSLException: Received fatal alert:
> bad_record_mac".
> Earlier versions of Maven used java.net.URLConnection which respects the
> https.protocols system property. This allowed us to set it to SSLv3, which is
> what our Maven repository uses. However, HttpClient ignores that property. In
> other situations, we programmatically tell HttpClient to use SSLv3, which we
> cannot do from our end.
> You can find another person in the same situation here:
> http://stackoverflow.com/questions/12787657/received-fatal-alert-bad-record-mac-when-deploying-to-sonatype
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
