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

Checking for existing gpg keys causes frequent keyring popups #757

Closed
sssoleileraaa opened this issue Feb 1, 2020 · 3 comments · Fixed by #793
Closed

Checking for existing gpg keys causes frequent keyring popups #757

sssoleileraaa opened this issue Feb 1, 2020 · 3 comments · Fixed by #793
Assignees

Comments

@sssoleileraaa
Copy link
Contributor

sssoleileraaa commented Feb 1, 2020

Description

"Keyring access from domain: sd-app" popup appears every time we sync. Once you see this every 15 seconds you stop closing the popup window and just expect it to be there the entire online lifetime of the client.

@eloquence
Copy link
Member

Why does the client have to access the keyring every time we sync, even if there are no changes?

@sssoleileraaa
Copy link
Contributor Author

Ah, it looks like this is the result of making a call to

def fingerprints(self) -> typing.Dict[str, bool]:
in order to make sure we don't import fingerprints that have already been imported.

@sssoleileraaa sssoleileraaa changed the title Frequent syncs means frequent qubes popups Checking for existing gpg keys causes frequent keyring popups Feb 1, 2020
@eloquence
Copy link
Member

Per @creviera the now highly frequent popups are extremely distracting. The high frequency also diminishes the value of these notifications as a security feature. Tracking as release blocker.

Per comment by @redshiftzero in standup today, if we set the fingerprint after successful key import, then we can only import key (i.e. access gpg keyring) if fingerprint column is null, which should reduce sd-gpg access to a reasonable level.

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

Successfully merging a pull request may close this issue.

3 participants