Open Bug 1530142 Opened 7 years ago Updated 3 years ago

Adding new secure function for memory clearing proposal

Categories

(NSPR :: NSPR, enhancement, P3)

enhancement

Tracking

(Not tracked)

People

(Reporter: devnexen, Unassigned)

Details

Attachments

(1 file)

Attached patch nspr.diffSplinter 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

Any opinion on this one ? :-)

Attachment #9046186 - Attachment is patch: true
Attachment #9046186 - Attachment mime type: text/x-patch → text/plain

Kai, can you comment here?

Assignee: nobody → devnexen
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Flags: needinfo?(kaie)
Priority: -- → P3

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?

Flags: needinfo?(kaie)

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.

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?

Severity: normal → S3

The bug assignee is inactive on Bugzilla, so the assignee is being reset.

Assignee: devnexen → nobody
Status: ASSIGNED → NEW
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: