Design CryptoWrapper (toolkit crypto API) XPCOM interface

NEW
Unassigned

Status

()

Core
DOM
6 years ago
4 months ago

People

(Reporter: ddahl, Unassigned)

Tracking

(Blocks: 3 bugs, {dev-doc-needed})

Trunk
dev-doc-needed
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

6 years ago
Create an XPCOM interface that exposes the DOMCrypt internal API, which can be used by chrome-privileged code. This interface will leave only the basic C++ apis inside PSM.
(Reporter)

Updated

6 years ago
Assignee: nobody → ddahl
(Reporter)

Updated

6 years ago
Blocks: 721199
(Reporter)

Updated

6 years ago
Blocks: 721200

Updated

6 years ago
Blocks: 636309
No longer blocks: 636309
(Reporter)

Updated

5 years ago
Summary: Implement DOMCrypt (Internal API) XPCOM interface → Design CryptoWrapper (toolkit crypto API) XPCOM interface
David, do you have any notes about the design of this?

I think that this API should be exactly the same as window.crypto or the worker variant of thta, but it should somehow be available without needing a reference to a DOM window. Is that what you're thinking too?
(Assignee)

Updated

5 years ago
Component: DOM: Mozilla Extensions → DOM
Product: Core → Core
(Reporter)

Updated

4 years ago
Assignee: ddahl → nobody

Comment 2

4 months ago
Outdated?
You need to log in before you can comment on or make changes to this bug.