aboutsummaryrefslogtreecommitdiff
path: root/lockchain-core/src/users/secrets.rs
diff options
context:
space:
mode:
Diffstat (limited to 'lockchain-core/src/users/secrets.rs')
-rw-r--r--lockchain-core/src/users/secrets.rs9
1 files changed, 5 insertions, 4 deletions
diff --git a/lockchain-core/src/users/secrets.rs b/lockchain-core/src/users/secrets.rs
index 2b4d45a..6c22293 100644
--- a/lockchain-core/src/users/secrets.rs
+++ b/lockchain-core/src/users/secrets.rs
@@ -1,6 +1,7 @@
//! A secrets type module that wraps around some user content with metadata
-use traits::AutoEncoder;
+use crate::traits::AutoEncoder;
+use serde::{Serialize, Deserialize};
/// Specifies the type of secret that's used to derive a vault user secret
#[derive(Serialize, Deserialize)]
@@ -16,14 +17,14 @@ pub enum SecretType {
impl AutoEncoder for SecretType {}
/// The backing secret for user authentication
-///
+///
/// This is _always_ in a non-recoverable form, i.e. a hash
/// and salted password. **However** it does reveal something
/// about the user setup, i.e. the type of secret used.
-///
+///
/// Depending on what secret is used, there are other operations that
/// might be supported to verify operations. For example, a `Keyfile`
-/// secret can deposit the entire public key in the `content` field,
+/// secret can deposit the entire public key in the `content` field,
/// then use asymmetric operations to verify operations more thoroughly.
#[derive(Serialize, Deserialize)]
pub struct UserSecret {