Closed
Bug 1281868
Opened 8 years ago
Closed 8 years ago
report of browser lock up using web Crypto in a ServiceWorker
Categories
(Core :: Security, defect)
Core
Security
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: bkelly, Assigned: bkelly)
References
Details
We were trying to find out why the guardian mobile labs push experiment only targeted chrome recently. They told us they ran into a browser deadlock when trying to use Crypto in a worker. We're collecting more details but wanted to get this filed so we had somewhere to put info. See: https://twitter.com/_alastair/status/746040158340976641
|
Assignee | |
Comment 1•8 years ago
|
||
They clarified this was an issue when using it in a ServiceWorker.
Summary: report of browser lock up using web Crypto in Worker thread → report of browser lock up using web Crypto in a ServiceWorker
|
|
Assignee | |
Updated•8 years ago
|
Component: Security → DOM: Security
|
|
Assignee | |
Comment 2•8 years ago
|
||
I think I see the problem.
|
|
Assignee | |
Updated•8 years ago
|
Assignee: nobody → bkelly
Status: NEW → ASSIGNED
|
||
Comment 3•8 years ago
|
||
What kind of crypto are they using? I can only think of webcrypto, which has been resolved in bug 842818 (landing in 48).
|
||
Updated•8 years ago
|
Component: DOM: Security → Security
Any updates here?
Flags: needinfo?(bkelly)
|
|
Assignee | |
Comment 5•8 years ago
|
||
I believe this was fixed by bug 1281874. I have not been able to get feedback from the original reporter, though. Marking closed for now.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Depends on: 1281874
Flags: needinfo?(bkelly)
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•