> Otherwise, I have tried "jdk.tls.client.protocols" system property, but
it does not achieve the desired effect.
Okay -- "jdk.tls.client.protocols" only disables SSL from a client
perspective ONLY. Akka remoting is from a server context. And
"https.protocol" is only good for an
That seems like a good catch indeed!
Thanks for finding this.
I've made an issue and PR for it:
https://github.com/akka/akka/issues/21077
https://github.com/akka/akka/pull/21078
If reviewed by team we could include this patch very soon.
Thanks for reporting!
-- Konrad
W dniu czwartek, 28
Thank you first for your reply :)
I add TLSv1 to jdk.tls.disabledAlgorithms of JRE java.security file, in
this way I can resolve the problem, but the modify will globally affect,
for example there is a java app needs TLSv1.
Otherwise, I have tried "jdk.tls.client.protocols" system property, but
You can set the "jdk.tls.client.protocols" system property to set options
for the JVM -- this is a feature that is only available in JDK 1.8 though.
https://docs.oracle.com/javase/8/docs/technotes/guides/security/SunProviders.html#SunJSSE_Protocols
Otherwise, you would have to set the security
Configure file as follow:
# Protocol to use for SSL encryption, choose from:
# Java 6 & 7:
# 'SSLv3', 'TLSv1'
# Java 7:
# 'TLSv1.1', 'TLSv1.2'
protocol = "TLSv1.2"
When I use nmap to scan, I find that TLSv1 is enabled:
D:\softwares\nmap-7.12>nmap -p --script=ssl* x.x.x.x
