974642 - Cryptographic primitives for chrome workers

Status: NEW

(Toolkit :: Async Tooling, defect)

Description

[David Teller [:Yoric] - still alive but not very active]

Bug 950522, bug 956713, possibly others, need some cryptographic APIs on chrome workers. Let's build them.

Comment 1

[:Gavin Sharp [email: [e-mail]]]

What kind of crypto primitives? Seems like potential overlap with bug 968567 and maybe bug 865789.

Comment 2

[Brian Smith (:briansmith, :bsmith, use NEEDINFO?)]

1. Please specify which primitives you want.
2. Can ChromeWorkers do XPCOM and/or js-ctypes?
3. If the answer to #2 is "no": Why do bug 950522 and bug 956713 have to be implemented as ChromeWorkers? Can they be implemented in a way that can access XPCOM or js-ctypes?

Comment 3

[David Teller [:Yoric] - still alive but not very active]

1. For the moment, the dependent bugs need the ability to compute hashes. This would be quite sufficient for our usecase in a first version.

2. ChromeWorkers cannot access XPCOM, but they can access js-ctypes, so we can certainly hook into nss if necessary.

3. These features need to be implemented as ChromeWorkers for performance reasons.

Comment 4

[Richard Barnes [:rbarnes]]

It seems to me like the easiest way to provide this would be to expose WebCrypto to workers, through the interface defined in the spec:
<https://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html#WorkerCrypto-interface>

Would that meet your needs?