This bug is marked Declined for Maverick by Sebastien Bacher. Can we
have an explanation? Is it an Ubuntu policy change regarding root login?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/484317
This behavior should be configurable, rather than forced. While I agree
that the default should be to forbid a root login with GDM, one should
be able to enable such functionality if they so choose.
--
GDM allows root logins
https://bugs.launchpad.net/bugs/484317
You received this bug
In response to #11, I confirm the bug is still present in Lucid.
jdr...@adjective-animal:~$ apt-cache policy gdm
gdm:
Installed: 2.30.2.is.2.30.0-0ubuntu3
Candidate: 2.30.2.is.2.30.0-0ubuntu3
Version table:
*** 2.30.2.is.2.30.0-0ubuntu3 0
500 http://ubuntu.media.mit.edu/ubuntu/
i'm glad it does, ctrl-alt-f1 doesn't seem to work anymore, sometimes
--
GDM allows root logins
https://bugs.launchpad.net/bugs/484317
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Can someone confirm if this bug is still the case in Lucid? If not, I'll
have a prep machine in a few days.
Also, if anyone has any direction on where this is heading, please let
me know also. Specifically, does this need patching? Or should the wiki
be updated to reflect the new behaviour of
And with regards to bug #459199, updated to match system uid
configuration.
Also, renamed it to disallow_invalid_login to better describe what it
does.
Regards
Iain
** Attachment added: 29_disallow_invalid_login.patch
http://launchpadlibrarian.net/37358835/29_disallow_invalid_login.patch
--
And imported all the relevant translations from gdm-2.20 into gdm-2.28
(using a perl script to grab+insert into files, so there may be error,
although I'm confident there isn't).
If anyone has any comments - greatly appreciated. As I'm learning here
as much as I am contributing.
Regards
Iain
@Kees, I agree.
This patch attached should do just that.
It's a slight modification of another part of the gdm code that
disallows the showing of system users in the selection screen. Copied it
into the do_accredit stage of the user authorisation, tested and it
works as expected.
Just putting
** Attachment added: 26_disallow_rootlogin.patch
http://launchpadlibrarian.net/37226490/26_disallow_rootlogin.patch
--
GDM allows root logins
https://bugs.launchpad.net/bugs/484317
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Even when a root password was set, gdm (Jaunty and prior) would not allow root
to log in:
The system administrator is not allowed to login from this screen
This behavior should be restored, but not via pam stack manipulations,
as it would lack the gdm-greeter feedback above.
--
GDM allows root
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/35788719/Dependencies.txt
--
GDM allows root logins
https://bugs.launchpad.net/bugs/484317
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Thankfully, the fix is trivial too:
Add the following to /etc/pam.d/gdm
authrequiredpam_succeed_if.so user != root quiet
Patch for the debian build attached.
Regards
Iain
** Attachment added: disallow_root_login.patch
Iain, I have attempted to reproduce this on Karmic Koala using UNR, but
root logins through the gdm is still results in authenication failure
for me. How exactly did you set the password for the root account?
** Changed in: gdm (Ubuntu)
Status: New = Incomplete
--
GDM allows root logins
I am able to reproduce this on a Lucid box using sudo passwd root to enable
the root account. I haven't heard that Ubuntu was going to allow root logins
through gdm even if the account is enabledf, so I believe this is a bug.
Thanks for your report, Iain.
** Changed in: gdm (Ubuntu)
Just running sudo passwd is enough to set the password.
Actually, after having a sleep on it, would it be useful just to deny
uid's 1000 and the 'nobody' user?
ie:
auth required pam_succeed_if.so uid = 1000 quiet
auth required pam_succeed_if.so user != nobody quiet
This, I think will restore
15 matches
Mail list logo
