-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix location of data #23
Conversation
This is a temporary fix until trussed gives us a way to have a per-backend store of data
9685358
to
1611df6
Compare
1611df6
to
04497d8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Please also update the doc comment for AuthBackend
with the new path.
This does mean that the salt is at
|
Should we move it to |
Let's move the global state to |
Current layout:
|
@@ -106,21 +107,21 @@ impl AuthBackend { | |||
|
|||
fn get_global_salt<R: CryptoRng + RngCore>( | |||
&self, | |||
trussed_filestore: &mut impl Filestore, | |||
global_fs: &mut impl Filestore, | |||
rng: &mut R, | |||
) -> Result<Salt, Error> { | |||
let path = PathBuf::from(BACKEND_DIR).join(&PathBuf::from("salt")); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wait, shouldn’t we drop BACKEND_DIR
here too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh right. It's even in the debugdumpstore just above
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should I do a 0.2.1 or just ovewrite the tag?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As we already pulled it into nitrokey-3-firmware, let’s use 0.2.1.
This is a temporary fix until trussed gives us a way to have a per-backend store of data