If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

CryptoHash module should be available from content processes

RESOLVED INVALID

Status

NSS
Libraries
RESOLVED INVALID
5 years ago
5 years ago

People

(Reporter: mounir, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
We need the CryptoHash component for bug 770532 but we currently can't use any NSS module from a content process.
(Reporter)

Comment 1

5 years ago
Unfortunately, it is not as trivial as not initializing NSS/PSM in the content process for CryptoHash. Initializing works but I've heard we would prefer to avoid some stuff to be available from the content process (maybe the opposite actually, just whitelist some that would be available).
(Reporter)

Updated

5 years ago
Blocks: 770833
(Reporter)

Updated

5 years ago
blocking-basecamp: --- → ?
(Reporter)

Updated

5 years ago
No longer blocks: 770833
(Reporter)

Comment 2

5 years ago
This is no longer needed for bug 770532.
No longer blocks: 770532
blocking-basecamp: ? → ---
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.