Closed Bug 1339373 Opened 9 years ago Closed 8 years ago

Reject "too much" early data sent by a client

Categories

(NSS :: Libraries, defect, P3)

Product:
NSS
Component:
Libraries
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: ttaubert, Unassigned)

References

Details

BoGo tests SkipEarlyData-TooMuchData and SkipEarlyData-HRR-TooMuchData test that a server should reject too much early data sent by a client. Boring currently defines too much starting at 16384 + 1.
See Also: → 1343036
I just tried to re-enable these tests, but they are somewhere between bad and awful. We currently don't have interoperability on the definition of the max_early_data_size field. It might be that I'm wrong about this and we shouldn't be calculating based on the plaintext size. I've started a thread on the tls@ietf mailing list and we'll see how that plays out.
Priority: -- → P3
It turns out that these tests are testing an internal feature of BoringSSL. We will never want to run those tests.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.