File: README.md

package info (click to toggle)
chromium 145.0.7632.159-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 5,976,224 kB
  • sloc: cpp: 36,198,469; ansic: 7,634,080; javascript: 3,564,060; python: 1,649,622; xml: 838,470; asm: 717,087; pascal: 185,708; sh: 88,786; perl: 88,718; objc: 79,984; sql: 59,811; cs: 42,452; fortran: 24,101; makefile: 21,144; tcl: 15,277; php: 14,022; yacc: 9,066; ruby: 7,553; awk: 3,720; lisp: 3,233; lex: 1,328; ada: 727; jsp: 228; sed: 36
file content (27 lines) | stat: -rw-r--r-- 1,196 bytes parent folder | download | duplicates (19) 
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).