Open
Bug 698243
Opened 14 years ago
Updated 2 years ago
nsNSSSocketInfo and nsSSLStatus are succeptable to race conditions
Categories
(Core :: Security: PSM, defect, P3)
Core
Security: PSM
Tracking
()
NEW
People
(Reporter: briansmith, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [psm-backlog])
In bug 686248, I attempt to avoid some rances caused by changes to mSSLStatus (in nsNSSSocketInfo) or to mServerCert (in nsSSLStatus) by copying the references into nsRefPtrs before using them, in case they are changed by another thread. However, nsSSLStatus needs locks to ensure that mServerCert is kept in sync with other attributes. nsNSSSocketInfo probably needs locks to ensure that the Read(), Write(), and main-thread-callable methods (mostly getters for nsITransportSecurityInfo attributes) don't race with operations on the SSL thread / socket transport thread.
| Reporter | ||
Comment 1•14 years ago
|
||
Don't forget that some nsNSSSocketInfo/nsSSLStatus methods that need modification are in nsIdentityChecking.cpp (and should be moved to where they belong).
Updated•9 years ago
|
Whiteboard: [psm-backlog]
Updated•8 years ago
|
Priority: -- → P2
Comment 4•7 years ago
|
||
Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
Updated•3 years ago
|
Severity: minor → S4
Updated•2 years ago
|
Blocks: nss-external
You need to log in
before you can comment on or make changes to this bug.
Description
•