Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Changing license | Katharina Fey | 2019-04-23 | 2 | -21/+678 |
| | | | | | | | | | | | | | Initially I decided lockchain should be an MIT licensed piece of software to allow a wide range of people and projects to use it. Thinking about it now, I feel that there are enough proprietary solutions for secret storage in the world. Whether that be pure password managers or enterprise-focused distributed secret stores. I don't know what lockchain will be one day or even what it is today, but I do know that I don't want it to become the backend to a proprietary piece of software. Therefore I have decided to relicense it under the GNU General Public License 3.0 or later. | ||||
* | Removing deprecated crypto engine functions (see 9ceda952) | Katharina Fey | 2019-04-22 | 4 | -55/+5 |
| | |||||
* | Running rustfmt | Katharina Fey | 2019-04-22 | 28 | -47/+45 |
| | |||||
* | Updating crates to 2018 edition (#9) | Katharina | 2019-04-22 | 41 | -1951/+374 |
| | | | | | | * Updating main README * Updating lock file * Updating crate ecosystem to Rust 2018 edition | ||||
* | Starting work on Keyfold | Katharina Fey | 2018-09-16 | 2 | -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 Fey | 2018-09-16 | 5 | -12/+20 |
| | | | | sense anymore 🤷 | ||||
* | Fixing documentation test cases | Katharina Fey | 2018-09-16 | 4 | -10/+15 |
| | |||||
* | Assorted changes | Katharina Fey | 2018-09-16 | 11 | -83/+139 |
| | |||||
* | Only relying on the `UserStore` `AutoEncoder` impl for serialisation | Katharina Fey | 2018-09-16 | 6 | -4/+36 |
| | |||||
* | Adding primitive file utilities | Katharina Fey | 2018-09-16 | 4 | -49/+87 |
| | |||||
* | A large batch of refactoring in FileVault | Katharina Fey | 2018-09-15 | 5 | -84/+117 |
| | | | | | | | | | | | | | | | | | | | | | | | | | Okay what am I doing here? If you're reading this in the future, it probably means I made some bad decisions. First: I'm sorry. Secondly: let me explain why I did what I did... Until this point `FileVault` has been a very transparent structure. It didn't really interact with the data much, basically solving all fs operations with streamed iterators and making sure stuff was done correctly, but not adding any depth on top of that. This needed to change... This isn't quite done and most of the code just breaks here ;) But the idea is to have `FileVault` be an intelligent wrapper around the filesystem. That means that not only does it cache certain operations for speed, it also keeps a selective index of files that exist. So for example, `Headers` were added here, that are always kept in sync with the FS. But only certain Records are stored (not only for security but also size consearns). After this refactoring is done (I shall write another long commit) the FileVault will act more as it's own type than just a simple, linear `Vault<T>` implementation. | ||||
* | Updating a bunch crates and generating keys | Katharina Fey | 2018-09-15 | 4 | -192/+239 |
| | |||||
* | Using the new generators to create filevault | Katharina Fey | 2018-09-15 | 7 | -72/+82 |
| | |||||
* | Restructuring internal layout and working on Generator intergration | Katharina Fey | 2018-09-15 | 3 | -54/+21 |
| | |||||
* | A lot of refactoring in lockchain-files | Katharina Fey | 2018-09-15 | 9 | -70/+123 |
| | |||||
* | Starting work on the lockchain-core --> lockchain-files userstore mapper | Katharina Fey | 2018-09-08 | 3 | -3/+23 |
| | |||||
* | Assorted code fixes | Katharina Fey | 2018-09-08 | 4 | -20/+29 |
| | |||||
* | Changing the vault trait to use Result<_, VaultError> more liberally | Katharina Fey | 2018-09-06 | 3 | -4/+10 |
| | |||||
* | Various smol changes around the new Generator API | Katharina Fey | 2018-09-06 | 5 | -78/+102 |
| | |||||
* | Removing deprecated `UserStore` and `KeyStore` into new `users::UserStore` | Katharina Fey | 2018-09-06 | 5 | -19/+27 |
| | | | | and fixing all resulting code issues | ||||
* | Refactoring the vault trait to consume a generator struct | Katharina Fey | 2018-09-06 | 6 | -213/+75 |
| | |||||
* | Now writing the config after vault scaffolding – woops. Making a small ↵ | Katharina Fey | 2018-09-04 | 3 | -45/+61 |
| | | | | example work | ||||
* | Cleaning up the core a bit. Adding better (any) config handling to files | Katharina Fey | 2018-09-04 | 12 | -91/+306 |
| | |||||
* | Generally refactoring some code (this is a bad commit message) | Katharina Fey | 2018-09-03 | 11 | -502/+714 |
| | |||||
* | Adding login/logout functions to the vault trait | Katharina Fey | 2018-08-06 | 3 | -17/+31 |
| | |||||
* | More refactoring and trying to get keystores to work properly | Katharina Fey | 2018-08-06 | 16 | -89/+91 |
| | |||||
* | Doing some file management, moving stuff around | Katharina Fey | 2018-08-06 | 14 | -86/+136 |
| | |||||
* | (cargo-release) start next development iteration 0.4.1-alpha.0 | Katharina Fey | 2018-07-12 | 2 | -5/+5 |
| | |||||
* | (cargo-release) version 0.4.0 | Katharina Fey | 2018-07-12 | 1 | -1/+1 |
| | |||||
* | (cargo-release) start next development iteration 0.9.1-alpha.0 | Katharina Fey | 2018-07-12 | 2 | -4/+4 |
| | |||||
* | (cargo-release) version 0.9.0 | Katharina Fey | 2018-07-12 | 1 | -1/+1 |
| | |||||
* | See previous commit message... | Katharina Fey | 2018-07-12 | 2 | -4/+4 |
| | |||||
* | (cargo-release) version 0.8.0 | Katharina Fey | 2018-07-12 | 1 | -1/+1 |
| | |||||
* | (cargo-release) start next development iteration 0.8.1-alpha.0 | Katharina Fey | 2018-07-12 | 2 | -5/+24 |
| | |||||
* | (cargo-release) version 0.8.0 | Katharina Fey | 2018-07-12 | 1 | -1/+1 |
| | |||||
* | Changing a bunch of version numbers around. This is really not a good solution | Katharina Fey | 2018-07-12 | 5 | -20/+56 |
| | | | | | I need a script that can do this automatically for releases because it's getting REALLY annoying and time consuming... | ||||
* | (cargo-release) start next development iteration 0.9.1-alpha.0 | Katharina Fey | 2018-07-12 | 2 | -2/+2 |
| | |||||
* | Bumping versions, updating dependencies | Katharina Fey | 2018-07-12 | 5 | -112/+112 |
| | |||||
* | (cargo-release) version 0.9.0 | Katharina Fey | 2018-07-12 | 2 | -2/+2 |
| | |||||
* | Adding a new keystore to lockchain-core::crypto, composing a userstore | Katharina Fey | 2018-07-12 | 6 | -33/+154 |
| | | | | | from two metadomains now (users, registry) to allow for a better user registry pipeline. Tweaking examples to make all this work and generally cleaning up code | ||||
* | Adding docs for `UserStore` | Katharina Fey | 2018-07-10 | 1 | -2/+8 |
| | |||||
* | Adding an example of how to register a user and adding new metadata | Katharina Fey | 2018-07-10 | 9 | -23/+158 |
| | | | | vault endpoints functions | ||||
* | Adding the http ability to register/login and managing metadata | Katharina Fey | 2018-07-10 | 1 | -0/+25 |
| | |||||
* | Adding access rights management functions | Katharina Fey | 2018-07-09 | 1 | -8/+16 |
| | |||||
* | Restoring the API handlers again, making it all work with the new | Katharina Fey | 2018-07-09 | 4 | -301/+249 |
| | | | | Error system (all stubs for now) | ||||
* | Refactoring the error modules to now contain sub-error types | Katharina Fey | 2018-07-09 | 12 | -189/+329 |
| | | | | | This isn't ideal yet but good enough for now. Errors can be added via a new variant in lockchain::errors::Error easily | ||||
* | Removing generics from error types | Katharina Fey | 2018-07-03 | 3 | -6/+27 |
| | |||||
* | Throwing stuff against walls | Katharina Fey | 2018-07-02 | 7 | -302/+355 |
| | |||||
* | This doesn't work | Katharina Fey | 2018-07-02 | 7 | -92/+67 |
| | |||||
* | Refactoring crypto module, moving `auth` into `users` module | Katharina Fey | 2018-07-02 | 11 | -118/+134 |
| |