Bug 680246 - screens not locked with fast user switching
screens not locked with fast user switching
Status: CLOSED DUPLICATE of bug 680065
Product: Fedora
Classification: Fedora
Component: gnome-shell (Show other bugs)
15
All Linux
urgent Severity urgent
: ---
: ---
Assigned To: Owen Taylor
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-02-24 14:32 EST by Jeff Bastian
Modified: 2011-02-24 14:46 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-02-24 14:46:00 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Jeff Bastian 2011-02-24 14:32:43 EST
Description of problem:
While working on the Graphics Test Day (http://fedoraproject.org/wiki/Test_Day:2011-02-24_Intel) I noticed during the fast-user-switch test that I can hit CTRL-ALT-F1 and CTRL-ALT-F7 to bounce between my two users and their screens are NOT locked.

If I use the [user menu]->Switch User option, then it asks for the password when switching users, but it's pretty easy to circumvent this security check with CTRL-ALT-Fn.

Please fix this security bug.

Version-Release number of selected component (if applicable):
gnome-shell-2.91.6-6.fc15

How reproducible:
every time

Steps to Reproduce:
1. Create two users and login as one to Gnome Shell
2. Use [user menu]->Switch User to login as the other user
3. Hit CTRL-ALT-F1 to switch back to the first user
4. Hit CTRL-ALT-F7 to switch back to the second user
  
Actual results:
switch users with no password

Expected results:
screens are locked when you switch away

Additional info:
Comment 1 Jeff Bastian 2011-02-24 14:46:00 EST
This sounds very similar to bug 680065, just triggered in a different way.  I'll mark this as a duplicate.

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

Note You need to log in before you can comment on or make changes to this bug.