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
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
|
***OS Crypt (Sync)***
This directory contains an `OSCrypt` implementation that supports cryptographic
primitives that allow binding data to the OS user. This is the legacy 'sync'
interface which should not be used in new code. Prefer using the 'async'
interface for any new code.
[os_crypt.h](os_crypt.h) contains the main interface.
The interface supports both instance based and a singleton interface, most
callers will use the singleton interface via convenience functions that handle
obtaining the singleton and calling directly into it. Advanced usage can
directly create an `OSCryptImpl` if needed, or access the singleton via
`GetInstance`.
Initialization is done per-process and can is usually done by calling the
platform-specific initialization function, which should take place before any
calls to encrypt or decrypt data occur.
* Linux - `SetConfig`
* Windows - `Init`
Alternatively, `OSCrypt` can be initialized with a key directly by using
`SetRawEncryptionKey` (or `InitWithExistingKey` - Windows only). This can also
be used to initialize OSCrypt in a non-browser process using a key supplied by
the browser.
The main functions are `EncryptString` and `DecryptString`. These can be called
on any thread and will return a user-bound encrypted string. It is guaranteed
that a string encrypted with `EncryptString` will be able to successfully
decrypt if `DecryptString` is called in the same user context. The exact
definition of user context is OS defined.
## Testing
The platform OSCrypt sync implementations have known-answer unit tests, which do
an encrypt-and-decrypt roundtrip and ensure that both the intermediate
ciphertext and the final plaintext match expected values. The reason for
known-answer tests, rather than ordinary roundtrip tests, is that the behavior
of OSCrypt for existing encrypted data on disk can't change without losing user
data. Without known-answer tests, it would be possible (for example) to change
key derivation in a way that did not break roundtrip tests but rendered all
existing user data undecryptable.
|
