sudoers update not working

t30_9

10/18/23, 11:56 AM

i would like to run an arping command in GitLab environment. For this i've a physical Runner where arping is running. The problem is that arping requires sudo authorisation. Of course this can not be done within GitLab pipeline.

sudo: no tty present and no askpass program specified

Therefore i was trying to configure the sudoers file by adding: USER ALL = NOPASSWD: /sbin/arping This is NOT working, and i can not understand why. Here is the result of "sudo -l"

User user may run the following commands on computer:
    (ALL : ALL) ALL
    (ALL) NOPASSWD: /sbin/arping

sudoers file:

Defaults        env_reset
Defaults        mail_badpass
Defaults        secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin"


# Cmnd alias specification

# User privilege specification
root    ALL=(ALL:ALL) ALL

# Members of the admin group may gain root privileges
%admin ALL=(ALL) ALL

# Allow members of group sudo to execute any command
%sudo   ALL=(ALL:ALL) ALL

# See sudoers(5) for more information on "#include" directives:

#includedir /etc/sudoers.d
user ALL=(ALL) NOPASSWD: /sbin/arping

Please note: the entry is at the bottom of the sudoers file.

Thank you a lot

133

0 + 0

permissions

command-line

sudo

arp

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: sudoers update not working

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.