Mirrors
/
open-keychain
mirror of https://github.com/open-keychain/open-keychain.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated Backups (markdown)

Dominik Schürmann 2016-01-07 16:26:50 +01:00
parent 3362a46e26
commit 00944bae9e
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Backups.md

@ -15,7 +15,7 @@ This is work in progress...
## Standard
1. All secret and public keys that should be included in the backup MUST be concatenated in their [transferable key format](http://tools.ietf.org/html/rfc4880#section-11.1).
2. A backup code is generated from secure random: The backup code consists of 24 upper case characters without ``O`` and ``0`` (``123456789ABCDEFGHJKLMNPQRSTUVWXYZ``) from the Latin alphabet grouped into 4-character chunks, e.g., ``TWNK-KDEY-MTWT-EVGS-DRDB-KVTW``. The characters MUST be generated from secure random, such as ``/dev/urandom``.
2. A backup code is generated from secure random: The backup code consists of 24 upper case characters and numbers without ``O`` and ``0`` (``123456789ABCDEFGHJKLMNPQRSTUVWXYZ``) from the Latin alphabet grouped into 4-character chunks, e.g., ``TWNK-KDEY-MTWT-EVGS-DRDB-KVTW``. The characters MUST be generated from secure random, such as ``/dev/urandom``.
3. The whole backup code including the dashes is directly used as a string to encrypt the concatenated transferable keys as an OpenPGP message (more precisely: It is used as the symmetric-key for a [Symmetric-Key Encrypted Session Key Packet](http://tools.ietf.org/html/rfc4880#section-5.3), the symmetric-key is thus 29 characters long including the dashes). The encryption algorithm MUST be one of the standardized OpenPGP symmetric algorithms (in case of OpenKeychain: AES-256).
## Saved as a file