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

Remove "remote-only storage of imported secrets" flow #139

Open
marsella opened this issue Oct 12, 2022 · 0 comments
Open

Remove "remote-only storage of imported secrets" flow #139

marsella opened this issue Oct 12, 2022 · 0 comments
Labels
committed This issue is required for this release

Comments

@marsella
Copy link
Contributor

marsella commented Oct 12, 2022

There are two import flows defined in the spec:

  1. Client-side, import a secret, encrypt it, and send the encrypted version to the server for storage.
  2. Client-side, import a secret and send it in the clear to the server (then delete it locally). Server-side, encrypt it and store it in potentially untrusted storage.

Right now, the spec requires both of these to be import flows to be implemented for both types of secret (arbitrary secrets and signing keys). However, flow 2 doesn't really make sense for arbitrary secrets; the server doesn't have any operations it can perform other on arbitrary secrets other than retrieving them, and that operation is also supported by flow 1. To adhere to our principle of least-trust on the server side, fix the spec to not allow flow 2 for arbitrary secrets.

At time of writing, this is not implemented, so this change will not result in any implementation tickets.

@LordQ1 LordQ1 added the committed This issue is required for this release label Oct 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
committed This issue is required for this release
Projects
None yet
Development

No branches or pull requests

2 participants