Events:
Because the call interface to upgrade to tls1.2 agreement, but my project is JDK1.6 environment, function, code mess can't upgrade to JDK1.8.

According to the Internet to jdk1.6 support tls1.2 protocol, the method of new TLSSocketConnectionFactory class and inherit SSLSocketFactory,
At the same time in httpsurlconnection. SetSSLSocketFactory (new TLSSocketConnectionFactory ());
But after the operation to Java. IO. IOException: Internal TLS error, this could be an attack,

If you use their implementation X509TrustManager to trust all certificates, you can only use the SSLContext,
Httpsurlconnection. SetSSLSocketFactory (sslcontext getSocketFactory ()); And is not an error, interface normal call,
Call interface is HTTP, not HTTPS,

Do test interface with each other not to upgrade to the tls1.2 agreement,




TLSSocketConnectionFactory code and send out an invitation card completely consistent,
https://blog.csdn.net/g5zhu5896/article/details/80429686#commentBox

Have a great god gives directions to know,

CodePudding user response:

First using TCP analysis software (caught) look at the consultation process

CodePudding user response:

To upgrade the JDK, don't, up
Refer to
https://stackoverflow.com/questions/33517476/tls-1-2-java-1-6-bouncycastle

The
90% of the time this works fine! But there are some cases in which we get an annoying error: "Internal TLS error, this could be an attack". It has had been checked that there is no attack. That 's a common error -based on the treatment of Internal BouncyCastle exceptions. I' m trying to find a common pattern to those remote host that fails with little luck.

CodePudding user response:

reference 4 floor stacksoverflow response:

upgrade JDK, don't toss.
Refer to
https://stackoverflow.com/questions/33517476/tls-1-2-java-1-6-bouncycastle

The
90% of the time this works fine! But there are some cases in which we get an annoying error: "Internal TLS error, this could be an attack". It has had been checked that there is no attack. That 's a common error -based on the treatment of Internal BouncyCastle exceptions. I' m trying to find a common pattern to those remote host that fails with little luck.

The system is convenient to upgrade the JDK, egg pain

CodePudding user response:

reference 5 floor monster9547 reply:

Quote: refer to 4th floor stacksoverflow response:

To upgrade the JDK, don't, up
Refer to
https://stackoverflow.com/questions/33517476/tls-1-2-java-1-6-bouncycastle

The
90% of the time this works fine! But there are some cases in which we get an annoying error: "Internal TLS error, this could be an attack". It has had been checked that there is no attack. That 's a common error -based on the treatment of Internal BouncyCastle exceptions. I' m trying to find a common pattern to those remote host that fails with little luck.

System is not convenient to upgrade the JDK, egg hurts

reference 5 floor monster9547 reply:

Quote: refer to 4th floor stacksoverflow response:

To upgrade the JDK, don't, up
Refer to
https://stackoverflow.com/questions/33517476/tls-1-2-java-1-6-bouncycastle

The
90% of the time this works fine! But there are some cases in which we get an annoying error: "Internal TLS error, this could be an attack". It has had been checked that there is no attack. That 's a common error -based on the treatment of Internal BouncyCastle exceptions. I' m trying to find a common pattern to those remote host that fails with little luck.

System is not convenient to upgrade the JDK, egg hurts

Seemingly jdk1.6.0 _121 - b09 support tls1.2
Refer to
https://www.oracle.com/technetwork/java/javase/overview-156328.html#R160_121

CodePudding user response:

refer to 6th floor stacksoverflow response:

Quote: refer to the fifth floor monster9547 reply:

Quote: refer to 4th floor stacksoverflow response:

To upgrade the JDK, don't, up
Refer to
https://stackoverflow.com/questions/33517476/tls-1-2-java-1-6-bouncycastle

The
90% of the time this works fine! But there are some cases in which we get an annoying error: "Internal TLS error, this could be an attack". It has had been checked that there is no attack. That 's a common error -based on the treatment of Internal BouncyCastle exceptions. I' m trying to find a common pattern to those remote host that fails with little luck.

System is not convenient to upgrade the JDK, egg hurts

reference 5 floor monster9547 reply:

Quote: refer to 4th floor stacksoverflow response:

To upgrade the JDK, don't, up
Refer to
https://stackoverflow.com/questions/33517476/tls-1-2-java-1-6-bouncycastle

The
90% of the time this works fine! nullnullnullnullnullnullnullnullnullnullnullnullnull