Closed
Bug 879674
Opened 11 years ago
Closed 10 years ago
WebCrypto: Implement importKey
Categories
(Core :: Security, defect)
Core
Security
Tracking
()
RESOLVED
DUPLICATE
of bug 995385
People
(Reporter: allstars.chh, Assigned: chucklee)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
6.47 KB,
patch
|
Details | Diff | Splinter Review | |
23.42 KB,
patch
|
Details | Diff | Splinter Review |
From http://www.w3.org/TR/WebCryptoAPI/#crypto-interface, we could start implementing 'importKey' interface, the current use case is this API could be used to import a PKCS 12 file. The question is that what value should be returnd in KeyOperation? Should it be the 'nickname' from NSS? And later we could use this 'nickname' to obtain the keys by CryptoKey.getKeysByName, See clause 7.3 from http://www.w3.org/TR/webcrypto-key-discovery/
Assignee | ||
Updated•11 years ago
|
Assignee: allstars.chh → chulee
Assignee | ||
Comment 1•11 years ago
|
||
Add WebIDL for WebCrypto.ImportKey() Some syntax are modified due to not supported or naming issue.
Assignee | ||
Comment 2•11 years ago
|
||
Just function declaration, no implementation yet.
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•