Github SSL / TLS protocol versions and the maven-changes-plugin configuration

74 views
Skip to first unread message

Lennart Jörelid

unread,
May 16, 2018, 1:55:42 PM5/16/18
to mojoha...@googlegroups.com
Hello all,

I just noticed something which may not be quite obvious:

  • Github's SSL service (api.github.com) does not support TLS version 1.0.
  • The standard HTTPS TLS version when running java is 1.0
  • Hence, the GitHub-report goal of the Maven-Changes-Plugin fails with an exception "javax.net.ssl.SSLException: Received fatal alert: protocol_version"
To remedy this, set the system property -Dhttps.protocols="TLSv1,TLSv1.1,TLSv1.2"

Should we do this within the mojo parent?
Currently, I don't think that plugin releases work properly using our configuration. Or am I mistaken?


--
+==============================+
| Bästa hälsningar,
| [sw. "Best regards"]
|
| Lennart Jörelid
| EAI Architect & Integrator
|
| jGuru Europe AB
| Mölnlycke - Kista
|
| Email: l...@jguru.se
| URL:   www.jguru.se
| Phone
| (skype):    jgurueurope
| (intl):     +46 708 507 603
| (domestic): 0708 - 507 603
+==============================+

Hervé Boutemy

unread,
May 16, 2018, 5:29:25 PM5/16/18
to mojohaus-dev
Hi,

Your analysis just misses the precise JDK version you're using: IIUC, you're using Oracle JDK 1.7u80 = the last Oracle public release
If you used 1.7u131 (from Oracle paying support or OpenJDK), you would not need the system property: see http://www.oracle.com/technetwork/java/javase/7u131-relnotes-3338543.html "Add TLS v1.1 and v1.2 to the client list of default-enabled protocols"

And of course, if you use Java 8, you don't need the option either

Regards,

Hervé
Reply all
Reply to author
Forward
0 new messages