From: Grant Taylor <gtaylor@gentoo.tnetconsulting.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Update to /etc/sudoers disables wheel users!!!
Date: Wed, 26 Oct 2022 13:26:54 -0600 [thread overview]
Message-ID: <d5e055d6-0d5b-94bb-8f8f-e2dcf8e1cc88@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <AM6PR10MB244072B23AC2FA84B29C14D3EF309@AM6PR10MB2440.EURPRD10.PROD.OUTLOOK.COM>
On 10/26/22 12:04 PM, Ramon Fischer wrote:
> Also a very interesting question!
}:-)
> I just tested this with "visudo" and it does not intercept this.
Nor should it.
It's perfect legitimate sudoers syntax.
The location; /etc/sudoers.d/zzzzzzzzzz vs the end of /etc/sudoers
(proper), doesn't matter.
> If "su" is disabled, you are locked out and you are forced to enter your
> system via a live USB stick and a "chroot" in order to edit
> "/etc/shadow" to set a root password via "mkpasswd" and enable "su".
Which is one of the reasons that it's important to have (set) a known
root password.
--
Grant. . . .
unix || die
next prev parent reply other threads:[~2022-10-26 19:27 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 2:34 [gentoo-user] Update to /etc/sudoers disables wheel users!!! Walter Dnes
2022-10-26 3:04 ` Ramon Fischer
2022-10-26 3:15 ` Grant Taylor
2022-10-26 3:34 ` Ramon Fischer
2022-10-26 3:40 ` Ramon Fischer
2022-10-26 3:44 ` Matt Connell
2022-10-26 16:21 ` Grant Taylor
2022-10-26 17:15 ` Neil Bothwick
2022-10-26 17:31 ` Rich Freeman
2022-10-26 20:17 ` Dale
2022-10-26 21:26 ` [gentoo-user] " Grant Edwards
2022-10-26 22:44 ` Dale
2022-10-27 1:23 ` Ramon Fischer
2022-10-27 3:01 ` Dale
2022-10-27 7:55 ` Ramon Fischer
2022-10-27 7:59 ` Ramon Fischer
2022-10-26 23:55 ` Rich Freeman
2022-10-26 6:31 ` [gentoo-user] " Walter Dnes
2022-10-26 7:42 ` Ramon Fischer
2022-10-26 11:31 ` Rich Freeman
2022-10-26 14:41 ` Ramon Fischer
2022-10-26 16:52 ` Grant Taylor
2022-10-26 17:12 ` [gentoo-user] " Grant Edwards
2022-10-26 17:54 ` Ramon Fischer
2022-10-26 18:04 ` [gentoo-user] " Ramon Fischer
2022-10-26 18:22 ` Neil Bothwick
2022-10-26 19:28 ` Grant Taylor
2022-10-26 20:08 ` Neil Bothwick
2022-10-26 20:17 ` Grant Taylor
2022-10-26 21:13 ` Neil Bothwick
2022-10-26 21:29 ` Grant Taylor
2022-10-26 21:48 ` Ramon Fischer
2022-10-26 23:06 ` Grant Taylor
2022-10-27 1:27 ` Ramon Fischer
2022-10-27 1:47 ` Grant Taylor
2022-10-27 7:53 ` Ramon Fischer
2022-10-26 18:35 ` Jack
2022-10-26 18:38 ` Ramon Fischer
2022-10-26 20:06 ` Neil Bothwick
2022-10-26 21:27 ` Ramon Fischer
2022-10-26 21:30 ` Grant Taylor
2022-10-26 19:31 ` Grant Taylor
2022-10-26 19:26 ` Grant Taylor [this message]
2022-10-26 18:04 ` Ramon Fischer
2022-10-26 16:38 ` Grant Taylor
2022-10-26 3:12 ` Matt Connell
2022-10-26 4:00 ` Anna “CyberTailor”
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d5e055d6-0d5b-94bb-8f8f-e2dcf8e1cc88@spamtrap.tnetconsulting.net \
--to=gtaylor@gentoo.tnetconsulting.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox