Ubuntu
gdm3 package

gdm3 writes user passwords to tty1

Bug #1782411 reported by Steffen on 2018-07-18

This bug report is a duplicate of: Bug #1767918: Login password from GDM is shown in plain text on the VT1 console. Edit Remove

258

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gdm3 (Ubuntu)	New	Undecided	Unassigned

Bug Description

After upgrading from 14.04 -> 16.04 -> 18.04 I recognized that all the gdm login keyboard input - that means user names and passwords - is written to the login console tty1.

# procedure to reproduce:

* graphical gdm login by selecting user and input password
* <login procedure>
* switch to tty1 by Ctrl-Alt-F1
* password(s) are visible on text console like STDERR
* after a few seconds the graphical login manager starts again

Note: at the moment I cannot reproduce that phenomenon - because Ctrl-Alt-F1 brings me only to the graphical gdm login manager anymore. The text console I do not see like before for some seconds.

Revision history for this message

Colin Watson (cjwatson) wrote on 2018-07-18:

Please don't file bugs against the "launchpad" project unless they're a problem with the launchpad.net site itself. I'm reassigning this closer to the right place (although it may in fact be a problem with how the console is set up; somebody will need to reproduce and debug in order to work that out).

affects:

launchpad → gdm3 (Ubuntu)

Revision history for this message

Marc Deslauriers (mdeslaur) wrote on 2018-07-27:

Making this bug public so it can be seen by the desktop developers.

information type:

Private Security → Public Security

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2018-07-30:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1767918, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.