Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8074462

Handshake messages can be strictly ordered

    XMLWordPrintable

    Details

    • Subcomponent:
    • Resolved In Build:
      b03
    • Verification:
      Verified

      Backports

        Description

        Per the spec of SSL/TLS specification, the handshake message is ordered. We have checked the sequence of key handshake messages. It's better to check the sequence of all handshake messages in case of any state issues.

          Attachments

            Issue Links

            backported by

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8207232 Handshake messages can be strictly ordered

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8207388 Handshake messages can be strictly ordered

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8208396 Handshake messages can be strictly ordered

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8211554 Handshake messages can be strictly ordered

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8212460 Handshake messages can be strictly ordered

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8213871 Handshake messages can be strictly ordered

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8216884 Handshake messages can be strictly ordered

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved
            relates to

            JEP - Java Enhancement Proposal JDK-8043758 JEP 219: Datagram Transport Layer Security (DTLS)

            • P1 - Blocks development and/or testing work, production could not run.
            • Closed

              Activity

                People

                • Assignee:
                  pkoppula Prasadarao Koppula
                  Reporter:
                  xuelei Xue-Lei Fan
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  8 Start watching this issue

                  Dates

                  • Due:
                    Created:
                    Updated:
                    Resolved: