US export laws relaxed The US export laws were crypto export in 1999. Crypto software can exported with minimal restrictions now. So the t-shirt is at this time legal to export as is the perl-rsa signature. The rest of this page is of historic value only.
It may be i that the RSA sig played some small part in the eventual relaxation of the US crypto export laws. Instructions for reverting changes are provided as a temporary workaround, in controlled environments, until the system can be updated to comply with the new security standards. Note that this is a low-risk change. It is unlikely to cause a regression since it just affects the order of the negotiated algorithms. 3DES would still be used, if listed on the legacy algorithm list, if no other non-legacy algorithm is available. DSA keys with sizes up to 2048 bits. Prior to this change, the maximum size was 1024 bits.
Note that these features were already supported on JDK 8 and JDK 9 Early Access. Applications may benefit from these new features when using security protocols or data that uses DSA keys or certificates. Applications are now able to verify certificates and TLS 1. Also, the keytool utility is now able to create and verify keypairs and certificates with these stronger algorithms and key sizes. To test this change download JDK 9.
1, 8u151, 7u161, 6u171, or later and set the system property jdk. Changing default TLS protocol version for client end points : TLS 1. 2 has been the default-enabled TLS protocol for JDK 8 since its release. Due to concerns around TLS version intolerance, TLS 1. 0 was left as the default enabled protocol for client end points on JDK 6 and JDK 7 when TLS 1. 2 was added to those releases. SSL, TLS protocols provide a built-in mechanism to negotiate the specific protocol version to use.
0 only might simply reject a client request for TLS 1. Even if the client would have been able to supports TLS 1. 0 a connection is not established. This property was introduced to JDK 7 in 7u95 and to JDK 6 in 6u121.
For example, if the value of this property is “TLSv1. 2”, then the default protocol settings on the client for TLSv1. 2 are enabled on the client, while SSLv3, TLSv1, and SSLv2Hello are disabled on the client. Set the client default protocol versions to TLS 1. Set the client default protocol version to TLS 1.
Note that the standard TLS protocol version names used in the JDK are SSLv3, TLSv1, TLSv1. Create SSLEngine object that enables TLS version 1. Create SSLSocket object that enables TLS version 1. An SSLContext with “TLSv1″ protocol supports TLS versions up to TLS 1. 1” supports versions up to TLS 1.