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

gpg key import not working in Qubes #363

Closed
redshiftzero opened this issue May 7, 2019 · 2 comments · Fixed by #377
Closed

gpg key import not working in Qubes #363

redshiftzero opened this issue May 7, 2019 · 2 comments · Fixed by #377
Assignees
Labels
bug Something isn't working qubes needed

Comments

@redshiftzero
Copy link
Contributor

Description

This was found while testing the securedrop-client-0.0.7 deb package in sd-svs, it looks like import of keys is not working, which means that encrypting a reply to a source won't work

STR

  1. start the client in Qubes
  2. submit a new document as a source
  3. click refresh

Expected behavior

source key is imported

Actual behavior

The following log line appears:

qubes-gpg-client: unrecognized option '--import-options'
@redshiftzero redshiftzero added bug Something isn't working qubes needed labels May 7, 2019
@eloquence eloquence added this to Near Term Backlog in SecureDrop Team Board May 7, 2019
@redshiftzero
Copy link
Contributor Author

(this isn't obvious due to the behavior described in #365)

@redshiftzero
Copy link
Contributor Author

we should use qubes-gpg-import-key for these import operations and then modify the qubes RPC policies to allow GpgImportKey from sd-svs (source) to sd-gpg (dest)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working qubes needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant