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

Add "passphraseless submission key" to prerequisites #95

Open
eloquence opened this issue Dec 21, 2021 · 3 comments
Open

Add "passphraseless submission key" to prerequisites #95

eloquence opened this issue Dec 21, 2021 · 3 comments

Comments

@eloquence
Copy link
Member

While our key generation docs suggest that it is safe to generate a passphraseless submission key, they do not strictly require it. It's certainly possible to use an SVS with a passphrase-protected key.
https://docs.securedrop.org/en/stable/generate_submission_key.html

Our SDW installation procedure and test plans do not currently account for a key protected by a passphrase. Until/unless this is a use case we explicitly support, I would suggest that we list a passphraseless submission key as a prerequisite for the SecureDrop Workstation.

@conorsch
Copy link
Contributor

conorsch commented Feb 7, 2022

Our SDW installation procedure and test plans do not currently account for a key protected by a passphrase. Until/unless this is a use case we explicitly support [...]

Given that split-gpg does not support passphrases on privkeys, we're not likely to change support anytime soon. Agree that clarification in the docs is the right approach.

@eaon
Copy link
Contributor

eaon commented Feb 7, 2022

That split-gpg doc is outdated then 😄 I use split-gpg with pinentry-gnome3 every day! But even so, the automated use from salt during initial setup that would make the use of passphrases on private keys cumbersome to support

@conorsch
Copy link
Contributor

conorsch commented Feb 7, 2022

That split-gpg doc is outdated then

Good to know! I was surprised to see the feature explicitly omitted, even though I don't use it myself. And the original point stands: we're not likely to support it on SDW in the foreseeable future.

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

3 participants