Skip to main content


Eclipse Community Forums

      Home
Home » Eclipse Projects » EGit / JGit » Failing to upload repo to github using eclipse 201912 -SSL protocol_version
Failing to upload repo to github using eclipse 201912 -SSL protocol_version [message #1818859] Mon, 30 December 2019 14:33 Go to next message
Eclipse UserFriend
Hi, everyone....

I'm a little baffled with this. I'm trying the usual forum solutions and they seem not to be working for me.

I'm trying to upload a project to 
github dot ibm dot com
(that is an enterprise github). Which I did fine with 201903 version.

The error shown is 
org.eclipse.jgit.api.errors.TransportException: WTF CENSORSHIP NOT ALLOWING ME TO PLACE AN HTTPS ADDRESS HERE :D 
	at org.eclipse.jgit.api.LsRemoteCommand.execute(LsRemoteCommand.java:222)
	at org.eclipse.jgit.api.LsRemoteCommand.call(LsRemoteCommand.java:161)
	at org.eclipse.egit.core.op.ListRemoteOperation.run(ListRemoteOperation.java:116)
	at org.eclipse.egit.ui.internal.components.AsynchronousListOperation.run(AsynchronousListOperation.java:78)
	at org.eclipse.egit.ui.internal.dialogs.CancelableFuture$1.run(CancelableFuture.java:280)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Caused by: org.eclipse.jgit.errors.TransportException: YETANOTHER CENSORSHIP NO I CANT PLACE A LINK HERE BECAUSE IM A NEW USER: cannot open git-upload-pack
	at org.eclipse.jgit.transport.TransportHttp.connect(TransportHttp.java:626)
	at org.eclipse.jgit.transport.TransportHttp.openFetch(TransportHttp.java:392)
	at org.eclipse.jgit.api.LsRemoteCommand.execute(LsRemoteCommand.java:200)
	... 5 more
Caused by: javax.net.ssl.SSLException: Received fatal alert: protocol_version
	at com.ibm.jsse2.k.a(k.java:32)
	at com.ibm.jsse2.k.a(k.java:37)
	at com.ibm.jsse2.av.b(av.java:549)
	at com.ibm.jsse2.av.a(av.java:715)
	at com.ibm.jsse2.av.i(av.java:574)
	at com.ibm.jsse2.av.a(av.java:280)
	at com.ibm.jsse2.av.startHandshake(av.java:431)
	at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:396)
	at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:355)
	at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142)
	at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:373)
	at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:394)
	at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:237)
	at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185)
	at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
	at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
	at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:108)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56)
	at org.eclipse.jgit.transport.http.apache.HttpClientConnection.execute(HttpClientConnection.java:261)
	at org.eclipse.jgit.transport.http.apache.HttpClientConnection.getResponseCode(HttpClientConnection.java:238)
	at org.eclipse.jgit.util.HttpSupport.response(HttpSupport.java:229)
	at org.eclipse.jgit.transport.TransportHttp.connect(TransportHttp.java:540)
	... 7 more


What did I try
1) Changed the running java to 1.8
2) Added the 
https.protocols=TLSv1.1,TLSv1.2 to the eclipse.ini



I've falled back to the 201903 version, and it works fine from there. Is there a new configuration I'm not aware about in the 201912 version?
Re: Failing to upload repo to github using eclipse 201912 -SSL protocol_version [message #1818890 is a reply to message #1818859] Tue, 31 December 2019 14:43 Go to previous messageGo to next message
Eclipse UserFriend
If you look in the EGit New & Noteworthy it says that EGit now uses Apache HTTP by default. If that doesn't work with whatever Java you're using (com.ibm.jsse2 is definitely not OpenJDK), you could switch back to the Java built-in client.

With OpenJDK using SSLContext.getInstance("TLS") creates sockets supporting TLSv1, TLSv1.1, and TLSv1.2 by default. What does the following code print on IBM JDK?

SSLContext context = SSLContext.getInstance("TLS");
context.init(null, null, null);
SSLSocketFactory factory = context.getSocketFactory();
SSLSocket socket = (SSLSocket) factory.createSocket();

String[] protocols = socket.getSupportedProtocols();
System.out.println("Supported Protocols: " + protocols.length);
for (String p : protocols) {
    System.out.println(" " + p);
}
protocols = socket.getEnabledProtocols();
System.out.println("Enabled Protocols: " + protocols.length);
for (String p : protocols) {
    System.out.println(" " + p);
}

What does this print if one uses "TLSv1.2" or "TLSv1.3" instead of "TLS"?

[Updated on: Tue, 31 December 2019 17:10] by Moderator

Re: Failing to upload repo to github using eclipse 201912 -SSL protocol_version [message #1818891 is a reply to message #1818890] Tue, 31 December 2019 14:56 Go to previous messageGo to next message
Eclipse UserFriend
Check also:

[Updated on: Tue, 31 December 2019 16:40] by Moderator

Re: Failing to upload repo to github using eclipse 201912 -SSL protocol_version [message #1818909 is a reply to message #1818891] Wed, 01 January 2020 10:58 Go to previous messageGo to next message
Eclipse UserFriend
I've opened bug 558709 for this.
Re: Failing to upload repo to github using eclipse 201912 -SSL protocol_version [message #1818918 is a reply to message #1818909] Thu, 02 January 2020 07:24 Go to previous messageGo to next message
Eclipse UserFriend
Yep, the change in git configurations by going to Window -> Preferences -> Team -> Git and setting the Http Client to the java built-in http did the trick for me... Thank you very much :)

BTW: for future releases, maybe it would be wise to make the default option to be the one that would make the application to behave like the previous version?

When you told me about the New and Noteworthy from eGit I've just asked "Whaaaaaaaaaaat???", making me to remember this: https://jasonkitcat.com/writings/e-democracy/updating-the-vogon-planning-process/ :D
Re: Failing to upload repo to github using eclipse 201912 -SSL protocol_version [message #1818921 is a reply to message #1818918] Thu, 02 January 2020 10:11 Go to previous messageGo to next message
Eclipse UserFriend
Re: Vogons

Yeah, that a new release of some software might have some release notes is really a surprise, isn't it. ;-)

It isn't really hidden. Every release of Eclipse comes with a "New & Noteworthy" page, the one for 2019-12 is linked there and is at https://www.eclipse.org/eclipseide/2019-12/noteworthy/ . The EGit New & Noteworthy in turn is linked there. Reading the release notes (i.e., New & Noteworthy pages) when upgrading is a good idea. :-) We could probably link to the EGit N&N from more places, though.

Re: Default setting:

No, we chose the new Apache HTTP as default setting on purpose to shake out bugs. The Apache HTTP client is not new code, and it has been well tested, but -- as I see now -- only on OpenJDK. Frankly said, that IBM in their infinite "wisdom" chose to implement this SSLContext.getInstance() differently than OpenJDK is a big surprise. But it's not a show-stopper; there's a work-around by setting that system property or by switching back to Java built-in HTTP, and the next release of EGit will contain code to make this work with Apache HTTP on IBM JDK without having to set that system property.
Re: Failing to upload repo to github using eclipse 201912 -SSL protocol_version [message #1819147 is a reply to message #1818921] Wed, 08 January 2020 13:53 Go to previous message
Eclipse UserFriend
You can also read the new and noteworthy in any Eclipse installation having EGit installed,
open "Windows > Help Content > EGit Documentation".

Meanwhile Thomas fixed the issue [1], if you update to the latest build from
https://download.eclipse.org/egit/updates-nightly
you can already benefit from the fix.

[1] https://git.eclipse.org/r/#/c/155130/
Previous Topic:Auto-create change-branch when pushing to gerrit
Next Topic:Switching Branches after Refactoring
Goto Forum:
  


Current Time: Wed Jul 23 08:04:46 EDT 2025

Powered by FUDForum. Page generated in 0.25296 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly