Johannes Rohr wrote: > Current versions of sudo fail to honour the NOPASSWD directive set for a > user/host/command set in /etc/sudoers: > > sudo -n apt-get update > sudo: a password is required > > /etc/sudoers says: > > xxx xxxx=NOPASSWD:/usr/bin/apt-get
I am not the maintainer but just another user. However this functionality is working correctly for me. For example I have this exact configuration for one example and it is operating. rwp ALL=(ALL) NOPASSWD: ALL What does your 'sudo -l' report? Specifically does it report the FQDN on this following line? $ sudo -l ... User rwp may run the following commands on havoc: ... > (of course, in the sudoers I have the real user and host names) The problem may be in your redacted hostname. See below. > I haven't changed the sudoers, so it must be a recent undocumented change in > programme behaviour. > The same configuration works just fine in Arch Linux. Could your case possibly be the hostname issue reported in Bug#813620? https://bugs.debian.org/813620 I don't experience that issue on my system either. I feel that the hostname problem may be related to the combination of hostname and /etc/hosts configuration. Reading it now I will post a question there. Bob
signature.asc
Description: PGP signature
