aboutsummaryrefslogtreecommitdiffstats
path: root/org.eclipse.jgit/src/org/eclipse/jgit/revwalk/BlockRevQueue.java
diff options
context:
space:
mode:
authorThomas Wolf <thomas.wolf@paranor.ch>2019-12-31 23:08:10 +0100
committerMatthias Sohn <matthias.sohn@sap.com>2020-01-03 20:48:25 +0100
commitd661b9f43a091a5b6b5d843f77e79856675435fb (patch)
tree842e48924121a8239e8ef3994d58f48be4cedc92 /org.eclipse.jgit/src/org/eclipse/jgit/revwalk/BlockRevQueue.java
parent9e6f09c7008171032ee0c0cccb34d7fa4b0ddeb6 (diff)
downloadjgit-d661b9f43a091a5b6b5d843f77e79856675435fb.tar.gz
jgit-d661b9f43a091a5b6b5d843f77e79856675435fb.zip
TLS support on IBM JDKs
SSLContext.getInstance("TLS") by default behaves differently on IBM JDK than on Oracle or OpenJDK.[1] On IBM JDK one gets sockets that have only TLSv1 enabled, which makes HTTPS connections fail since most servers refuse this old protocol version. On Oracle JDK/OpenJDK, one gets sockets with all available protocol versions enabled. Explicitly enable all available TLS protocol versions to make HTTPS connections work also on IBM JDK. [1] https://www.ibm.com/support/knowledgecenter/en/SSYKE2_8.0.0/com.ibm.java.security.component.80.doc/security-component/jsse2Docs/matchsslcontext_tls.html#matchsslcontext_tls Bug: 558709 Change-Id: I5ffc57a78e67a6239b9dad54840a49a8ed28930a Signed-off-by: Thomas Wolf <thomas.wolf@paranor.ch> Signed-off-by: Matthias Sohn <matthias.sohn@sap.com>
Diffstat (limited to 'org.eclipse.jgit/src/org/eclipse/jgit/revwalk/BlockRevQueue.java')
0 files changed, 0 insertions, 0 deletions