aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Deprecating the entire `lockchain-crypto` API because it makes no gosh darn ↵Katharina Fey2018-09-165-12/+20
| | | | sense anymore 🤷
* Fixing documentation test casesKatharina Fey2018-09-164-10/+15
|
* Assorted changesKatharina Fey2018-09-1611-83/+139
|
* Only relying on the `UserStore` `AutoEncoder` impl for serialisationKatharina Fey2018-09-166-4/+36
|
* Adding primitive file utilitiesKatharina Fey2018-09-164-49/+87
|
* A large batch of refactoring in FileVaultKatharina Fey2018-09-155-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 keysKatharina Fey2018-09-154-192/+239
|
* Using the new generators to create filevaultKatharina Fey2018-09-157-72/+82
|
* Restructuring internal layout and working on Generator intergrationKatharina Fey2018-09-153-54/+21
|
* A lot of refactoring in lockchain-filesKatharina Fey2018-09-159-70/+123
|
* Starting work on the lockchain-core --> lockchain-files userstore mapperKatharina Fey2018-09-083-3/+23
|
* Assorted code fixesKatharina Fey2018-09-084-20/+29
|
* Changing the vault trait to use Result<_, VaultError> more liberallyKatharina Fey2018-09-063-4/+10
|
* Various smol changes around the new Generator APIKatharina Fey2018-09-065-78/+102
|
* Removing deprecated `UserStore` and `KeyStore` into new `users::UserStore`Katharina Fey2018-09-065-19/+27
| | | | and fixing all resulting code issues
* Refactoring the vault trait to consume a generator structKatharina Fey2018-09-066-213/+75
|
* Now writing the config after vault scaffolding – woops. Making a small ↵Katharina Fey2018-09-043-45/+61
| | | | example work
* Cleaning up the core a bit. Adding better (any) config handling to filesKatharina Fey2018-09-0412-91/+306
|
* Generally refactoring some code (this is a bad commit message)Katharina Fey2018-09-0311-502/+714
|
* Adding login/logout functions to the vault traitKatharina Fey2018-08-063-17/+31
|
* More refactoring and trying to get keystores to work properlyKatharina Fey2018-08-0616-89/+91
|
* Doing some file management, moving stuff aroundKatharina Fey2018-08-0614-86/+136
|
* (cargo-release) start next development iteration 0.4.1-alpha.0Katharina Fey2018-07-122-5/+5
|
* (cargo-release) version 0.4.0Katharina Fey2018-07-121-1/+1
|
* (cargo-release) start next development iteration 0.9.1-alpha.0Katharina Fey2018-07-122-4/+4
|
* (cargo-release) version 0.9.0Katharina Fey2018-07-121-1/+1
|
* See previous commit message...Katharina Fey2018-07-122-4/+4
|
* (cargo-release) version 0.8.0Katharina Fey2018-07-121-1/+1
|
* (cargo-release) start next development iteration 0.8.1-alpha.0Katharina Fey2018-07-122-5/+24
|
* (cargo-release) version 0.8.0Katharina Fey2018-07-121-1/+1
|
* Changing a bunch of version numbers around. This is really not a good solutionKatharina Fey2018-07-125-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.0Katharina Fey2018-07-122-2/+2
|
* Bumping versions, updating dependenciesKatharina Fey2018-07-125-112/+112
|
* (cargo-release) version 0.9.0Katharina Fey2018-07-122-2/+2
|
* Adding a new keystore to lockchain-core::crypto, composing a userstoreKatharina Fey2018-07-126-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 Fey2018-07-101-2/+8
|
* Adding an example of how to register a user and adding new metadataKatharina Fey2018-07-109-23/+158
| | | | vault endpoints functions
* Adding the http ability to register/login and managing metadataKatharina Fey2018-07-101-0/+25
|
* Adding access rights management functionsKatharina Fey2018-07-091-8/+16
|
* Restoring the API handlers again, making it all work with the newKatharina Fey2018-07-094-301/+249
| | | | Error system (all stubs for now)
* Refactoring the error modules to now contain sub-error typesKatharina Fey2018-07-0912-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 typesKatharina Fey2018-07-033-6/+27
|
* Throwing stuff against wallsKatharina Fey2018-07-027-302/+355
|
* This doesn't workKatharina Fey2018-07-027-92/+67
|
* Refactoring crypto module, moving `auth` into `users` moduleKatharina Fey2018-07-0211-118/+134
|
* Big code change & refactoring commitKatharina Fey2018-07-029-12/+160
| | | | | | | | | Move `token` into user module for lockchain-core. Start work on a PAM authentication module which replaces the second layer UserStore in API layer state (http being the only one for now). This brings the `nix` and `pam-auth` dependencies, which unfortunately currently don't work :(
* Refactoring models module, adding more inputsKatharina Fey2018-07-016-20/+106
|
* Fleshing out REST API fully and adding function stubsKatharina Fey2018-06-303-27/+130
|
* Adding default implementations for load and saveKatharina Fey2018-06-301-9/+36
|
* Ironing out some problems with the ApiState serialisationKatharina Fey2018-06-302-18/+6
|