Closed Bug 1550874 Opened 4 months ago Closed 4 months ago

Don't call SSL_SetResumptionToken if SSL_NO_CACHE option was set on the socket

Categories

(Core :: Networking, defect, P2)

defect

Tracking

()

RESOLVED FIXED
mozilla68
Tracking Status
firefox68 --- fixed

People

(Reporter: michal, Assigned: michal)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged])

Attachments

(1 file)

This is a follow up bug of bug 1546975. We shouldn't search the cache and try to set TLS resumption token in nsSocketTransport::InitiateSocket() if the socket has SSL_NO_CACHE flag set, because NSS code might not honor the flag when the token is provided via API for external TLS session caches.

We shouldn't search the cache and try to set TLS resumption token in nsSocketTransport::InitiateSocket() if the socket has SSL_NO_CACHE flag set, because NSS code might not honor the flag when the token is provided via API for external TLS session caches.

Pushed by mnovotny@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/705cbeee6d09
Don't call SSL_SetResumptionToken if SSL_NO_CACHE option was set on the socket, r=valentin
Status: NEW → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
You need to log in before you can comment on or make changes to this bug.