Skip to content
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

Export key derivation options #33

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Conversation

Gudahtt
Copy link
Member

@Gudahtt Gudahtt commented Nov 4, 2022

Key derivation options are now exported from the functions keyFromPassword and encryptWithDetail. This can allow the project using this package to store the key derivation options alongside the vault, allowing for easier migrations to newer derivation options in the future.

Closes #1

@Gudahtt Gudahtt force-pushed the export-encryption-details branch 2 times, most recently from 82efed9 to afc318d Compare November 4, 2022 06:21
Key derivation options are now exported from the functions
`keyFromPassword` and `encryptWithDetail`. This can allow the project
using this package to store the key derivation options alongside the
vault, allowing for easier migrations to newer derivation options in
the future.
@Gudahtt Gudahtt force-pushed the export-encryption-details branch from afc318d to 26cf6a5 Compare November 4, 2022 06:28
@Gudahtt Gudahtt changed the title Export encryption details Export key derivation options Nov 4, 2022
@Gudahtt
Copy link
Member Author

Gudahtt commented Nov 7, 2022

I don't think this is valuable until we support some alternative options. Putting this on the backburner until we decide on how to improve our key generation.

@danfinlay
Copy link
Contributor

One easy way to improve generation would be to simply add more hash cycles. Current vaults could be made harder to crack.

@Gudahtt
Copy link
Member Author

Gudahtt commented Nov 14, 2022

Yeah, maybe for now we can add support just for that. And we can set a minimum of the current number of cycles that we use.

I would like to preserve a minimum level of safety with the options we allow. That's the only reason I'm hesitating to allow further configuration; I don't know how to ensure a minimum level of safety across all of these controls.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Store key derivation function used and iteration count in payload
3 participants