Closed
Bug 1428894
Opened 8 years ago
Closed 8 years ago
Unable to save private CryptoKeys in IndexedDB
Categories
(Core :: DOM: Security, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1048931
People
(Reporter: sarah.gilkinson, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36
Steps to reproduce:
Attempt to save a private CryptoKey to IndexedDB.
(http://zl.kg.gg/ for example)
Actual results:
The private CryptoKey failed to save, and produced "errorDataCloneError: The object could not be cloned."
Expected results:
The private CryptoKey should have been saved to IndexedDB.
Comment 1•8 years ago
|
||
Build ID: 20180111100722
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0
Reproducible on Firefox Nightly 59.0a1, Firefox 58.0b15, Firefox 57.0.4 on Windows 10 x 64, Mac OS X 10.12 and Ubuntu 16.04 x64.
status-firefox57:
--- → affected
status-firefox58:
--- → affected
status-firefox59:
--- → affected
Component: Untriaged → DOM: Security
Product: Firefox → Core
Updated•8 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Comment 3•5 years ago
|
||
Hello!
I hope you are doing great!
Are there any updates about this?
We are not supporting Firefox for one of our products because of this issue :/
Thanks!
You need to log in
before you can comment on or make changes to this bug.
Description
•