The latest version of Chrome (45.0.2454.85 m), when accessing the certificate, will report "The server's instantaneous
Diffie-hellman public key Too weak "
The first thought is the issue of certificate production, Baidu saw a solution is to set up Tomcat
Level of confidentiality: join in <connector>
Ciphers= "tls_ecdhe_rsa_with_aes_128_cbc_sha256,tls_ecdhe_rsa_with_aes_128_
Cbc_sha,tls_ecdhe_rsa_with_aes_256_cbc_sha384,tls_ecdhe_rsa_with_aes_256_c
Bc_sha,tls_rsa_with_aes_128_cbc_sha256,tls_rsa_with_aes_128_cbc_sha,tls_rs
A_with_aes_256_cbc_sha256,tls_rsa_with_aes_256_cbc_sha "
But in this machine test, the online environment will be reported: Unsupported cipher suite XXX
Tests have found that the encryption algorithms supported by JDK1.6 and JDK1.7 are not the same, testing the upgrade JDK
, problem solving.
Transient Diffie-hellman public key for server is too weak