Skip to content

8301626: Capture Named Group information in TLSHandshakeEvent#31371

Open
seanjmullan wants to merge 2 commits into
openjdk:masterfrom
seanjmullan:open6
Open

8301626: Capture Named Group information in TLSHandshakeEvent#31371
seanjmullan wants to merge 2 commits into
openjdk:masterfrom
seanjmullan:open6

Conversation

@seanjmullan
Copy link
Copy Markdown
Member

@seanjmullan seanjmullan commented Jun 3, 2026

This change adds the negotiated named group to the JFR TLSHandshakeEvent.



Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8301626: Capture Named Group information in TLSHandshakeEvent (Enhancement - P3)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/31371/head:pull/31371
$ git checkout pull/31371

Update a local copy of the PR:
$ git checkout pull/31371
$ git pull https://git.openjdk.org/jdk.git pull/31371/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 31371

View PR using the GUI difftool:
$ git pr show -t 31371

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/31371.diff

Using Webrev

Link to Webrev Comment

@seanjmullan seanjmullan marked this pull request as ready for review June 3, 2026 14:22
@bridgekeeper
Copy link
Copy Markdown

bridgekeeper Bot commented Jun 3, 2026

👋 Welcome back mullan! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link
Copy Markdown

openjdk Bot commented Jun 3, 2026

❗ This change is not yet ready to be integrated.
See the Progress checklist in the description for automated requirements.

@openjdk openjdk Bot added security security-dev@openjdk.org core-libs core-libs-dev@openjdk.org hotspot-jfr hotspot-jfr-dev@openjdk.org labels Jun 3, 2026
@openjdk
Copy link
Copy Markdown

openjdk Bot commented Jun 3, 2026

@seanjmullan The following labels will be automatically applied to this pull request:

  • core-libs
  • hotspot-jfr
  • security

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command.

@openjdk openjdk Bot added the rfr Pull request is ready for review label Jun 3, 2026
@mlbridge
Copy link
Copy Markdown

mlbridge Bot commented Jun 3, 2026

Webrevs

// handshake context cleanup.
chc.handshakeFinished = true;
recordEvent(chc.conContext.conSession);
recordEvent(chc);
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We record an event both on consuming and on producing Finished:

  • Would there be any difference between those 2 events? AFAICT all the event's fields should be equal.
  • How do we differentiate between consuming and producing events?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nevermind, I see now that we actually log only once on each side: client producing and server consuming.

public String protocolVersion;
public String cipherSuite;
public long certificateId;
public String namedGroup;
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: namedGroup is being logged right after cipherSuite, it will be consistent to keep the same order here and in src/jdk.jfr/share/classes/jdk/jfr/events/TLSHandshakeEvent.java

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core-libs core-libs-dev@openjdk.org hotspot-jfr hotspot-jfr-dev@openjdk.org rfr Pull request is ready for review security security-dev@openjdk.org

Development

Successfully merging this pull request may close these issues.

2 participants