aboutsummaryrefslogtreecommitdiff
path: root/lockchain-core/src/crypto/data.rs
diff options
context:
space:
mode:
authorKatharina Fey <kookie@spacekookie.de>2018-09-16 18:41:49 +0100
committerKatharina Fey <kookie@spacekookie.de>2018-09-16 18:41:49 +0100
commit9ceda952a1c0d42b11a67dd7d00178c720f9c601 (patch)
tree83af0919b50d9b9a4e91772f9bfdef288d2baeda /lockchain-core/src/crypto/data.rs
parentf7c0e6d59dc420d73916083af1dfd95a8b4c6fc9 (diff)
Starting work on Keyfold
The idea here is the following: You don't want to have to write encryption code for keys all the time especially if there are many and maybe lots of interactions. Also...maybe you doN't have the raw key anymore. It's kept in the vault in encrypted form and you just cache it from time to time. So you get it, decrypt it, store it in the Engine again, do some crypto. The user forgets about you, the key is cleared..etc. The keyfold comes in right there! It takes care of decrypting and re-encrypting any keychanges made by the user, so that the Vault backend only ever gets encrypted keys to work with.
Diffstat (limited to 'lockchain-core/src/crypto/data.rs')
0 files changed, 0 insertions, 0 deletions