Bug 1060428 - GDM catches password after blank screen
Summary: GDM catches password after blank screen
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gdm
Version: 20
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-01 16:25 UTC by Jimmy Thrasibule
Modified: 2015-06-29 14:55 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-29 14:55:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jimmy Thrasibule 2014-02-01 16:25:00 UTC
Description of problem:

GDM will catch any keyboard inputs and set it as password for the next user to log in after a blank screen.


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

Fedora 20
 * gdm-3.10.0.1-1.fc20.x86_64


How reproducible:

This can be reproduced any time.


Steps to Reproduce:

1. Boot up the system and leave login screen untouched until screen goes blank.
2. Enter something using the keyboard, screen light up on user selection screen.
3. Click on any user.
 

Actual results:

Password field is already filed.


Expected results:

Password field should be empty.


Additional info:

This is a strong security issue for a user entering his/her password and leaving. Someone can just select the user and connect because the password has been filed already.

Comment 1 Fedora End Of Life 2015-05-29 10:46:04 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2015-06-29 14:55:16 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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