Closed Bug 1828713 Opened 2 years ago Closed 22 days ago

Intermittent [ FAILED ] GreaseTests/GreasePresenceAbsenceTestAllVersions.ClientGreaseKeyShare/7, where GetParam() = (1, 772, false)

Categories

(NSS :: Libraries, defect, P3)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jschanck, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: intermittent-failure)

Attachments

(1 file)

Failing job: https://treeherder.mozilla.org/jobs?repo=nss&selectedTaskRun=C8OSLKAYQQO0Zst1a4hK8w.0

Relevant log output:

Version: DTLS 1.3
server: Changing state from INIT to CONNECTING
client: Changing state from INIT to CONNECTING
client: Handshake success
client: Changing state from CONNECTING to CONNECTED
server: Handshake success
server: Changing state from CONNECTING to CONNECTED
Connected with version 772 cipher suite TLS_AES_128_GCM_SHA256
../../gtests/ssl_gtest/tls_grease_unittest.cc:63: Failure
Expected equality of these values:
  expected
    Which is: 1
  countGreaseInBuffer(buffer)
    Which is: 2
client: Warning alert sent: 0
[  FAILED  ] GreaseTests/GreasePresenceAbsenceTestAllVersions.ClientGreaseKeyShare/6, where GetParam() = (1, 772, true) (6 ms)

The severity field is not set for this bug.
:beurdouche, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(bbeurdouche)

Anna, can you please check priority and severity ? : ) Thanks !

Flags: needinfo?(bbeurdouche) → needinfo?(nkulatova)
Severity: -- → S4
Priority: -- → P3

I observed this. It fails randomly, that really surprises me.

Flags: needinfo?(nkulatova)

Still failing today (example)

Summary: Intermittent failure in GreaseTests/GreasePresenceAbsenceTestAllVersions.ClientGreaseKeyShare → Intermittent [ FAILED ] GreaseTests/GreasePresenceAbsenceTestAllVersions.ClientGreaseKeyShare/7, where GetParam() = (1, 772, false)

countGreaseInBuffer scanned the entire raw key_share extension buffer, including
the random key_exchange bytes of real key shares (e.g., 32 bytes for x25519).
Any aligned 2-byte window in that random data matching a GREASE pattern caused a
spurious count of 2 instead of 1. Fix by parsing the extension structurally and
only checking the group ID fields.

Pushed by jschanck@mozilla.com:
https://hg.mozilla.org/projects/nss/rev/a5c520d5b666
Fix intermittent ClientGreaseKeyShare test failure. r=nss-reviewers,djackson

Status: NEW → RESOLVED
Closed: 22 days ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: