Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1013576

Summary:	suspend/hibernate does not lock ssh and gpg keys
Product:	Red Hat Enterprise Linux 7	Reporter:	Paolo Bonzini <pbonzini>
Component:	gnome-keyring	Assignee:	Zeeshan Ali <zeenix>
Status:	CLOSED WONTFIX	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.1	CC:	mclasen, pbonzini
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-12-06 19:07:42 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Paolo Bonzini 2013-09-30 11:21:39 UTC

Description of problem:
If someone steals my laptop while it is suspended, my password lets them read my encrypted email and send signed messages that impersonate me.  They can also log into my machines.  This goes against my usage of different passphrases for ssh, gpg and machines.

Version-Release number of selected component (if applicable):
3.8

How reproducible:
100%

Steps to Reproduce:
1. Start a GNOME session
2. ssh to a machine using your public key
3. suspend and resume (or hibernate and resume)
4. ssh to a machine using your public key

Actual results:
Steps 2 prompts for the passphrase.

Expected results:
Steps 2 and 4 prompt for the passphrase.

Additional info:
The same behavior is present for the GPG agent.
The GNOME keyring is locked/unlocked at suspend/resume.

Comment 2 Zeeshan Ali 2013-12-06 19:07:42 UTC

If you enable 'Screen Lock' in gnome-control-center's 'Privacy' settings, your thief wont have access to anything unless they know your password.

Comment 3 Paolo Bonzini 2013-12-09 10:07:49 UTC

It is enabled already, of course.

But my GPG passphrase is different from my password for a reason.  If people have gotten my password by looking over my shoulder, they won't be able to impersonate me in signed pull requests, for example.  (Stealing my password over my shoulder is much easier than stealing my GPG key, since I use the GPG key much less).