aboutsummaryrefslogtreecommitdiff
path: root/lockchain-crypto/src (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Updating crates to 2018 edition (#9)Katharina2019-04-224-29/+22
| | | | | | * Updating main README * Updating lock file * Updating crate ecosystem to Rust 2018 edition
* Starting work on KeyfoldKatharina Fey2018-09-162-25/+91
| | | | | | | | | | | | | | | | 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.
* Deprecating the entire `lockchain-crypto` API because it makes no gosh darn ↵Katharina Fey2018-09-163-4/+13
| | | | sense anymore 🤷
* Adding some user registration codeKatharina Fey2018-06-291-0/+6
|
* Changing lockchain-core::crypto to keybob keys. then updating allKatharina Fey2018-06-281-14/+19
| | | | references in lockchain-crypto to use it instead.
* Adjusting to new lockchain-core traitsKatharina Sabel2018-05-121-8/+8
|
* Bumping version on core and cryptoKatharina Fey2018-05-093-40/+47
|
* Fixing an issue with the lockchain-core crypto APIKatharina Fey2018-05-082-4/+3
|
* Changing the way that vault traits workKatharina Fey2018-05-083-128/+0
|
* Basic encryption functions workKatharina Sabel2018-05-086-11/+215
|
* Restructuring traits that handle encryption moduleKatharina Sabel2018-05-083-31/+52
|
* Shuffling some stuff around and implementing some traitsKatharina Sabel2018-05-071-5/+40
|
* More refactoring across the skyKatharina Fey2018-05-061-0/+7