This bug is there to track the addition of TLS_FALLBACK_SCSV support to OpenJDK. There is some discussion upstream: <http://mail.openjdk.java.net/pipermail/security-dev/2015-February/011688.html> Webrev: <http://cr.openjdk.java.net/~fweimer/8061798/webrev.00/> I'm not saying we absolute have to apply this *now*, but I'll try to convince upstream to implement this proactively, rather than waiting for requests to implement this coming in.
Do you have a version of this for 8 already? We can't alter SSLParameters in 8 or below, as it's part of the Java API.
For 8, I plan to backport only the server-side change, and we'll have to test it with another client (either the 9 client, or OpenSSL). On upstream's security-dev list, there has been a push to handle this via the regular cipher suite selection, but I'm strongly opposed to that because it is asking for developers and system administrators for abusing this feature.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Latest webrev and review request: http://mail.openjdk.java.net/pipermail/security-dev/2015-August/012624.html http://cr.openjdk.java.net/~fweimer/8061798/webrev.03/
What's the latest status of this?
(In reply to Andrew John Hughes from comment #5) > What's the latest status of this? I don't know. There still seems to be some upstream interest, but I don't know the exact state. Is there still a compelling reason to implement TLS_FALLBACK_SCSV? I'm no longer sure if it is necessary—I think browsers have stopped doing out-of-protocol fallback.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
I don't think this feature is necessary anymore because insecure protocol downgrade has been phased out from the client population.