File: README.md

package info (click to toggle)
chromium 141.0.7390.107-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 6,246,132 kB
  • sloc: cpp: 35,264,965; ansic: 7,169,920; javascript: 4,250,185; python: 1,460,635; asm: 950,788; xml: 751,751; pascal: 187,972; sh: 89,459; perl: 88,691; objc: 79,953; sql: 53,924; cs: 44,622; fortran: 24,137; makefile: 22,313; tcl: 15,277; php: 14,018; yacc: 8,995; ruby: 7,553; awk: 3,720; lisp: 3,096; lex: 1,330; ada: 727; jsp: 228; sed: 36
file content (27 lines) | stat: -rw-r--r-- 1,196 bytes parent folder | download | duplicates (17) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
 
# Web Crypto

This directory contains the cryptographic code for Chromium's [Web
Crypto](https://www.w3.org/TR/WebCryptoAPI/) implementation.

The Web Crypto implementation is split between Blink and this directory.

Blink is responsible for parsing Web Crypto's Web IDL, and translating requests
into method calls on `blink::WebCrypto`, which in turn is implemented here by
[WebCryptoImpl](webcrypto_impl.h).

`WebCryptoImpl` is what carries out the actual cryptographic operations. Crypto
is done directly in the renderer process, in software, using BoringSSL. There is
intentionally no support for hardware backed tokens.

Threading:

The Web Crypto API expects asynchronous completion of operations, even when
used from Web Workers. `WebCryptoImpl` takes a blanket approach of dispatching
incoming work to a small worker pool. This favors main thread
responsiveness/simplicity over throughput. Operations minimally take two thread
hops.

The split of responsibilities between Blink and `content`
(`content` is what registers `blink::WebCrypto` to the Blink Platform) is dated
and could be simplified. See also
[crbug.com/614385](https://bugs.chromium.org/p/chromium/issues/detail?id=614385).