[arch-general] root login @ console
So I foo-bared my /home partition, no big deal, done it before, and I keep good backups. I boot to single mode and get to a prompt. My regular user is gone so I try to just login at the console (no X) as root. It doesn't work. I know I set the root password. What setting is preventing root from being able to authenticate. I noticed when I went to cups on localhost:631 and tried to do an admin task and needed to authenticate. Root couldn't login. How do I allow root logins under Arch/Arco linux at a console???
On 11/13/20 10:06 AM, Jack Frost via arch-general wrote:
So I foo-bared my /home partition, no big deal, done it before, and I keep good backups. I boot to single mode and get to a prompt. My regular user is gone so I try to just login at the console (no X) as root. It doesn't work. I know I set the root password.
What setting is preventing root from being able to authenticate. I noticed when I went to cups on localhost:631 and tried to do an admin task and needed to authenticate. Root couldn't login.
How do I allow root logins under Arch/Arco linux at a console???
Can you try chroot-ing in using a live USB?
Yes, that works fine. I am still left not being able to login as root
though. What setting is causing that in Arch?
On Fri, Nov 13, 2020 at 11:09 AM Yash Karandikar via arch-general
On 11/13/20 10:06 AM, Jack Frost via arch-general wrote:
So I foo-bared my /home partition, no big deal, done it before, and I keep good backups. I boot to single mode and get to a prompt. My regular user is gone so I try to just login at the console (no X) as root. It doesn't work. I know I set the root password.
What setting is preventing root from being able to authenticate. I noticed when I went to cups on localhost:631 and tried to do an admin task and needed to authenticate. Root couldn't login.
How do I allow root logins under Arch/Arco linux at a console???
Can you try chroot-ing in using a live USB?
On Fri, 13 Nov 2020 at 16:06, Jack Frost via arch-general
So I foo-bared my /home partition, no big deal, done it before, and I keep good backups. I boot to single mode and get to a prompt. My regular user is gone so I try to just login at the console (no X) as root. It doesn't work. I know I set the root password.
What setting is preventing root from being able to authenticate.
In a runlevel S console perhaps the keymap isn't set, try typing in a visible field to check if you use special chars in your passwd.
On Fri Nov 13, 2020 at 11:06 AM EST, Jack Frost via arch-general wrote:
What setting is preventing root from being able to authenticate. I noticed when I went to cups on localhost:631 and tried to do an admin task and needed to authenticate. Root couldn't login.
Perhaps the root account is locked with `passwd -l root`? You can try and check by looking through the `/etc/passwd` file. If after `root:` is an `!` or a `*`, then you won't be able to login.
How do I allow root logins under Arch/Arco linux at a console???
Assuming you have access to the bootloader, you can try "Using bash as init"[1] or the other options on the Wiki page. [1]: https://wiki.archlinux.org/index.php/Reset_lost_root_password#Using_bash_as_... - Steven
Le vendredi 13 novembre 2020 17:06:08 CET Jack Frost via arch-general a écrit :
So I foo-bared my /home partition, no big deal, done it before, and I ...
Had a somehow similar problem yesterday. After removing all lines with 'pam_tally' in /etc/pam.d/login via ssh (fortunately worked), I could login as root at console. This module is reportedly deprecated. If there's a login.pacnew file, just replace the current login file with the pacnew one, unless you have custom settings in your login file. Regards.
Thanks for the tip. There were no pam.d/ files that had pam_tally and
now pacnew files. I am digging through pam man pages to see if I can
figure it out. Someone had to disable root access. I commented out
pam_securetty.so in all the files but still no luck.
Thanks.
On Fri, Nov 13, 2020 at 5:04 PM SET via arch-general
Le vendredi 13 novembre 2020 17:06:08 CET Jack Frost via arch-general a écrit :
So I foo-bared my /home partition, no big deal, done it before, and I ...
Had a somehow similar problem yesterday.
After removing all lines with 'pam_tally' in /etc/pam.d/login via ssh (fortunately worked), I could login as root at console. This module is reportedly deprecated.
If there's a login.pacnew file, just replace the current login file with the pacnew one, unless you have custom settings in your login file.
Regards.
Op za 14 nov. 2020 03:50 schreef Jack Frost via arch-general < arch-general@archlinux.org>:
Thanks for the tip. There were no pam.d/ files that had pam_tally and now pacnew files. I am digging through pam man pages to see if I can figure it out. Someone had to disable root access. I commented out pam_securetty.so in all the files but still no luck.
You could also try reading the logs... (probably journald). When the authentication fails, there is surely some message somewhere stating /why/ it failed. Mvg, Guus
Nov 14 13:35:28 yoda audit[2683212]: USER_AUTH pid=2683212 uid=0
auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=?
acct="root" exe="/usr/bin/login" hostname=yoda addr=? terminal=tty2
res=failed'
Nov 14 13:35:28 yoda kernel: audit: type=1100
audit(1605378928.928:6994): pid=2683212 uid=0 auid=4294967295
ses=4294967295 msg='op=PAM:authentication grantors=? acct="root"
exe="/usr/bin/login" hostname=yoda addr=? terminal=tty2 res=failed'
Nov 14 13:35:31 yoda login[2683212]: FAILED LOGIN 1 FROM tty2 FOR
root, Authentication failure
I read somewhere that I could tell pam to use debug output. I will
see if I can find that.
Thanks for the tip.
On Sat, Nov 14, 2020 at 11:15 AM Guus Snijders via arch-general
Op za 14 nov. 2020 03:50 schreef Jack Frost via arch-general < arch-general@archlinux.org>:
Thanks for the tip. There were no pam.d/ files that had pam_tally and now pacnew files. I am digging through pam man pages to see if I can figure it out. Someone had to disable root access. I commented out pam_securetty.so in all the files but still no luck.
You could also try reading the logs... (probably journald).
When the authentication fails, there is surely some message somewhere stating /why/ it failed.
Mvg, Guus
participants (6)
-
Guus Snijders
-
Jack Frost
-
NTS
-
SET
-
Steven Guikal
-
Yash Karandikar