After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 527341 - 'Leave Message' feature does reveal clipboard contens after screen lock
'Leave Message' feature does reveal clipboard contens after screen lock
Status: RESOLVED DUPLICATE of bug 482159
Product: gnome-screensaver
Classification: Deprecated
Component: general
2.20.x
Other All
: Normal normal
: ---
Assigned To: gnome-screensaver maintainers
gnome-screensaver maintainers
Depends on:
Blocks:
 
 
Reported: 2008-04-10 13:03 UTC by Florian Walther
Modified: 2008-04-10 22:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Florian Walther 2008-04-10 13:03:36 UTC
Please describe the problem:
If you copy and past (e.g. a password) and then lock your screen and go away someone else can walk to your computer can click 'Leave Message' and press Ctrl+V in order to reveal the password (or whatever content) you had in your clipboard before you locked the screen.

Steps to reproduce:
1. copy and paste some sensitive information
2. Lock your screen
3. 'Leave Message' and press Ctrl+V to see the formerly copied password


Actual results:
gnome-screensaver helps attackers to revela your copied passwords (or other possibly sensitive information)

Expected results:
Since there is this "leave a message" feature I would expect the screensave to clear the clipboard before activation.

Does this happen every time?
Yes

Other information:
no further information available, i hope it's clear what i talk about.
Comment 1 Ray Strode [halfline] 2008-04-10 22:21:48 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in versions 2.21.6 and later . You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 482159 ***