Decrypting backup with AES-256 in GCM mode.
Depends on D8999
Details
Details
Encrypt/decrypt different types of both UserData and UserData.
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
| native/backup/encryption.js | ||
|---|---|---|
| 59 ↗ | (On Diff #30479) | if we were able to decrypt, it means it exactly the same object as we encrypted so we can assume the type without additional validation |
| native/backup/conversion-utils.js | ||
|---|---|---|
| 19 ↗ | (On Diff #30479) | This function (and its counterpart) should be in a generic place. Directory native/utils/ looks like the right place. |
| native/backup/conversion-utils.js | ||
|---|---|---|
| 19 ↗ | (On Diff #30479) | I have mixed feelings about this idea... name is generic but it's placed on purpose in this directory. A case when we will need to take bytes (which are bytes of UTF-8 string) and convert it to string, and then parse it because this string is JSON is something really backup related, not generic. |