public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ramon Fischer <Ramon_Fischer@hotmail.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Update to /etc/sudoers disables wheel users!!!
Date: Wed, 26 Oct 2022 20:04:57 +0200	[thread overview]
Message-ID: <AM6PR10MB24402B6ACD69233295640C17EF309@AM6PR10MB2440.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <e19fda7e-8611-fcbf-a275-ccf8a2ea1fd3@spamtrap.tnetconsulting.net>


[-- Attachment #1.1.1: Type: text/plain, Size: 1029 bytes --]

Indeed, an intersting question, which you actually already answered 
yourself. I just tested it myself:

    $ visudo -f /etc/sudoers.d/00-wheel
         %wheel ALL=(ALL) ALL

    $ sudo --list
         User ramon may run the following commands on <some_hostname>:
             (ALL) ALL

    $ sudo -f /etc/sudoers.d/00-wheel
         # negate the entry
         !wheel ALL=(ALL) ALL

    $ sudo --list
         User ramon may run the following commands on <some_hostname>:
             Entry is gone

-Ramon

On 26/10/2022 18:52, Grant Taylor wrote:
> What are end users / systems administrators to do if the default file 
> has something like the following enabled in the default /etc/sudoers 
> file and the EUs / SAs want it to not be there?
>
>    %wheel ALL=(ALL:ALL) ALL
>
> They have no choice but to change (edit / replace) the /etc/sudoers file. 

-- 
GPG public key: 5983 98DA 5F4D A464 38FD CF87 155B E264 13E6 99BF


[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 8969 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  parent reply	other threads:[~2022-10-26 18:05 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
2022-10-26 18:04         ` Ramon Fischer [this message]
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=AM6PR10MB24402B6ACD69233295640C17EF309@AM6PR10MB2440.EURPRD10.PROD.OUTLOOK.COM \
    --to=ramon_fischer@hotmail.de \
    --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