Open Bug 1545813 Opened 3 years ago Updated 7 months ago

Can't Clone CryptoKey when algorithm is ECDSA

Categories

(Core :: DOM: Web Crypto, defect, P2)

67 Branch
defect

Tracking

()

Tracking Status
firefox66 --- affected
firefox67 --- affected
firefox68 --- affected

People

(Reporter: qmatillat, Unassigned)

Details

Attachments

(1 file)

Attached file index.html

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:67.0) Gecko/20100101 Firefox/67.0

Steps to reproduce:

Generate an ECDSA key
Save it in indexedDB
(see index.html that reproduce this issue)

Actual results:

The keys are not stored in database, with the error "DataCloneError: The object could not be cloned."

Expected results:

The keys should be stored in database (as it occur with other keys type, like RSA-PSS)

tested on Ubuntu 16.04 with:
66.0.3 20190409155332
68.0a1 20190423095327

I can see the reported console error using the index.html test scenario, but I cannot say if the test case is valid or not. Let's move out of untriaged for a better informed opinion.

Status: UNCONFIRMED → NEW
Component: Untriaged → DOM: Web Crypto
Ever confirmed: true
Product: Firefox → Core

Yep. WebCrypto work is not high priority presently, but this should be something we fix as soon as we've time to touch WebCrypto again.

Severity: normal → major
Priority: -- → P2

According to this comment PKCS is used internally while it is not supported. Why not simply use JWK for the time being? It would avoid application developers to have to use exportable keys, and it could be changed in a later release.

You need to log in before you can comment on or make changes to this bug.