Cryptographic Key Storage

[fd0]

Regarding your first question: @cfbao found a limit of 1000 bytes (which I wasn’t even aware of). Since we’re applying a key-derivation function (scrypt), a much shorter password (20-25 characters if you want to make sure) is plenty. See also here:

What if keys are compromised?

All data in the repo is encrypted (and signed) with the “master keys”. In order to decrypt the “master keys”, you need the content of a key file together with the correct password. The data in the N, r, p and salt attributes of the JSON document together with the password are used with the scrypt() key derivation function (KDF) to compute a set of keys, which can then be used to decrypt the master keys in the data attribute. The crux is that evaluating the scrypt() function to get the keys fro…