-
Bug
-
Resolution: Fixed
-
P2
-
8u261
-
b01
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8252994 | 8u271 | Dmitry Markov | P2 | Closed | Fixed | b08 |
JDK-8253150 | 8u261 | Dmitry Markov | P2 | Closed | Fixed | b36 |
JDK-8257265 | emb-8u281 | Dmitry Markov | P2 | Resolved | Fixed | team |
JDK-8253884 | emb-8u271 | Dmitry Markov | P2 | Resolved | Fixed | team |
JDK 8u261 shipped with deploy having the ability to detect if TLSv1.3 support was available and use it if so.
For now, deploy stack should use the same policy as the main TLS JDK stack and disable TLSv1.3 by default.
For now, deploy stack should use the same policy as the main TLS JDK stack and disable TLSv1.3 by default.
- backported by
-
JDK-8253884 Disable TLSv1.3 by default on deploy configurations
- Resolved
-
JDK-8257265 Disable TLSv1.3 by default on deploy configurations
- Resolved
-
JDK-8252994 Disable TLSv1.3 by default on deploy configurations
- Closed
-
JDK-8253150 Disable TLSv1.3 by default on deploy configurations
- Closed
- relates to
-
JDK-8279518 Enable TLSv1.3 by default on deploy configurations
- Closed