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 timestamp to split-gpg keychain access log #1835

Open
mfc opened this Issue Mar 15, 2016 · 2 comments

Comments

Projects
None yet
3 participants
@mfc
Member

mfc commented Mar 15, 2016

this bug was reported at the Internet Freedom Festival.

From a usability and security perspective it would be good for the user to know a place where these notifications are logged (ideally viewable with a GUI, and have timestamps). Otherwise a malicious, compromised tbird could just decrypt emails etc when the user is not looking at their computer.

@mfc mfc added bug UX labels Mar 15, 2016

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 24, 2016

Member

Access is logged in log of calling VM: /var/log/qubes/qrexec.VMNAME.log. Unfortunately without a timestamp...

Member

marmarek commented Mar 24, 2016

Access is logged in log of calling VM: /var/log/qubes/qrexec.VMNAME.log. Unfortunately without a timestamp...

@mfc

This comment has been minimized.

Show comment
Hide comment
@mfc

mfc Mar 24, 2016

Member

so maybe the first step is to have timestamp. then later for an ability to view it from a gui, or have some shortcut to it. i'm going to switch this to a feature request for now.

Member

mfc commented Mar 24, 2016

so maybe the first step is to have timestamp. then later for an ability to view it from a gui, or have some shortcut to it. i'm going to switch this to a feature request for now.

@mfc mfc added enhancement and removed bug labels Mar 24, 2016

@mfc mfc changed the title from split-gpg keychain access notification is not logged in KDE notifications (are they logged elsewhere?) to add timestamp to split-gpg keychain access log May 24, 2016

@andrewdavidwong andrewdavidwong added this to the Far in the future milestone Dec 24, 2016

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