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

Desired characteristics of derived keys #18

Open
jans23 opened this issue Apr 10, 2020 · 2 comments
Open

Desired characteristics of derived keys #18

jans23 opened this issue Apr 10, 2020 · 2 comments

Comments

@jans23
Copy link
Member

jans23 commented Apr 10, 2020

Relates to #15.

Questions

  • Do we want to prevent device tracking?
  • Do we want to use per-origin keys usually? -> Prefer key_handle to prevent collision.
  • Do we want to use cross-orign keys usually? -> Prefer key_index for easier usage.

key_index (e.g. 1 byte)

  • Is easier to use

key_handle (e.g. 32 byte)

  • Is a kind of access token, which prevents device/user tracking (privacy issue)
  • Needs to be provided (copied) by user for each service to use the key.

Unless decided, the device could use a key handle between 1 and 32 byte, which covers both options above.

@jans23
Copy link
Member Author

jans23 commented Apr 10, 2020

@onlykey what do you think?

@szszszsz
Copy link
Member

szszszsz commented Apr 10, 2020

This would provide an opportunity to implement a 'hidden key' (similar to 'hidden volume' in 'encrypted volume') by providing the key handle by the user in a form of passphrase, and calculating the PBKDF2 of it (resulting of the 32-bytes key_handle).

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

No branches or pull requests

2 participants