Adding new secure function for memory clearing proposal
Categories
(NSPR :: NSPR, enhancement, P3)
Tracking
(Not tracked)
People
(Reporter: devnexen, Unassigned)
Details
Attachments
(1 file)
|
2.02 KB,
patch
|
Details | Diff | Splinter Review |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_3) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/12.0.3 Safari/605.1.15
Updated•7 years ago
|
Comment 2•7 years ago
|
||
Kai, can you comment here?
Comment 3•7 years ago
|
||
We'd require an implementation that achieves the promised behavior on all platforms.
Are you certain your implementation does that?
Can you show why using memset, combined with a volatile function pointer, guarantees that it isn't optimized away, on all platforms?
It seems some platforms offer the system library call explicit_bzero. Why not use it on those platforms?
I knew about explicit_bzero (explicit_memset for NetBSD) etc ... it was basically to reduce the ifdef ... lines but if preferred we can go with the platform specific solutions.
Comment 5•7 years ago
|
||
What's the motivation behind this? Why should anyone prefer to use a NSPR function rather than use what's provided by the C standard?
Updated•3 years ago
|
Comment 6•3 years ago
|
||
The bug assignee is inactive on Bugzilla, so the assignee is being reset.
Description
•