DataCloneError storing unextractable ECDSA private key in indexedDB
Categories
(Core :: Storage: IndexedDB, defect, P2)
Tracking
()
People
(Reporter: matt, Assigned: janv)
References
Details
Attachments
(2 files)
Updated•8 years ago
|
Comment 2•7 years ago
|
||
Assignee | ||
Comment 3•7 years ago
|
||
![]() |
||
Comment 4•7 years ago
|
||
Comment 5•7 years ago
|
||
![]() |
||
Comment 6•7 years ago
|
||
Comment 7•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!
As of Firefox 89, I have confirmed that it is possible to export an ECDH private key marked as "extractable" at generation in the "jwk" format. (Though the original issue was filed regarding ECDSA keys, I've observed the exact same problem with ECDH keys, so I'm presuming a common underlying problem.)
This seems to imply that the underlying limitation in NSS mentioned by Dana Keeler is no longer the limiting factor here, since I can export the key in some format. (It also seems to imply that underlying NSS extraction limitations aren't whats keeping bug 1133698 open anymore either, since although PKCS8 export still doesn't work I am able to export in JWK.)
However, I still get a data clone error when trying to store the ECDH private key in IndexedDB. That seems to indicate to me that even though bug 1133698 is still open, it does not seem to be what's causing the remaining problem here.
Could someone more knowledgeable than myself review this issue again, and if my observations and inference are correct re-open this issue to resolve the remaining data-clone problem that remains despite ECC private key export now working?
Thank you!
![]() |
||
Comment 9•4 years ago
|
||
Joel - please open a new bug with example code of what you've encountered that should work but doesn't.
Comment 11•4 years ago
|
||
Hi Dana :D Fission.codes, Mirror.xyz and localForage are all hitting this some version of this issue.
Can you advise on the right way to narrow down what the problem is, so that we can file the bug in the right way so it doesn't get closed?
https://github.com/fission-suite/keystore-idb/issues/1
https://github.com/localForage/localForage/issues/844#issuecomment-556553007
https://twitter.com/strangechances/status/1446285765810352128
Based on at least one of those comments, sounds like Chrome works fine but Safari might have a similar problem so I'll poke about Webkit as well to see if we can work towards full web platform compat!
Updated•4 years ago
|
![]() |
||
Comment 12•4 years ago
|
||
Hi Dietrich :)
So this is still broken in Firefox 93? (just released this week, I think)
If so, the best way to narrow this down is to find a reduced test case that illustrates the issue (the attachment in comment 0 appears to work for me). Once I have something relatively small and self-contained it'll be much easier to see what the problem is.
Comment 13•4 years ago
|
||
Updated the testcase to cover ECDH, which was the problem reported in comment #8, and also to cover extractable and not extractable for RSA, ECDSA and ECDH.
Works in latest release and nightly versions of Firefox, and latest release version of Safari!
So never mind - looks like this working. I'm going to share on those various issues and if they report issues will bring it back around again :)
![]() |
||
Comment 14•4 years ago
|
||
Great - thanks!
Description
•