/qubes-issues

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-split compatibility with Torbirdy #1796

Closed
marmarek opened this Issue Feb 29, 2016 · 1 comment

Comments

Assignees
No one assigned
Labels
Projects
None yet
Milestone
No milestone
1 participant
@marmarek
@marmarek
Member

marmarek commented Feb 29, 2016

Clone of https://trac.torproject.org/projects/tor/ticket/14025

Since there is no much interest from Tor developers, maybe we can simply ignore --keyserver-options in qubes-gpg-client-wrapper? This might have some negative impact if GPG VM is not really offline, but that would be misuse of gpg-split anyway.

cc @adrelanos

@marmarek marmarek added enhancement C: other P: minor labels Feb 29, 2016

marmarek added a commit to marmarek/qubes-app-linux-split-gpg that referenced this issue Feb 29, 2016

@marmarek
Ignore --keyserver-options 
This option is forcefully set by Torbirdy extension and it is cumbersome
to get rid of it. So to make gpg-split compatible with Torbirdy, simply
ignore the option. See linked ticket for more details.

Fixes QubesOS/qubes-issues#1796
Verified
This commit was signed with a verified signature.
@marmarek marmarek Marek Marczykowski-Górecki
GPG key ID: 063938BA42CFA724 Learn about signing commits
cd069c9

@marmarek marmarek referenced this issue in marmarek/qubes-app-linux-split-gpg Feb 29, 2016

Merged

Ignore --keyserver-options #1

@marmarek marmarek added the duplicate label Feb 29, 2016

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 29, 2016

Member

There is already ticket for it: #1024
Member

marmarek commented Feb 29, 2016

There is already ticket for it: #1024

@marmarek marmarek closed this Feb 29, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment