Date: Mon, 18 Aug 2014 16:28:01 -0700 From: Jungle Boogie <jungleboogie0@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: What Would Make Sudo Always Let one Execute a Command? Message-ID: <53F28C01.8060800@gmail.com> In-Reply-To: <20140818210721.0EEDB22957@server1.shellworld.net> References: <20140818210721.0EEDB22957@server1.shellworld.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Dear Martin, -------------------------------------------- From: Martin G. McCormick <martin@server1.shellworld.net> Sent: Mon, 18 Aug 2014 16:07:21 -0500 To: freebsd-questions@freebsd.org Subject: What Would Make Sudo Always Let one Execute a Command? > > Sudo behaves as if the default timeout in sudoers was set to -1. > Out of 5 FreeBSD9 systems, this one system exhibits this > behavior while all the others time out like they should. Setting > the value to 0 should cause one to always have to enter a > password, but not on this system. > Has anyone ever seen this before? The sudoers file is a > copy of the same sudoers file we use on the other machines. I > have also tried sudo from a few other user ID's on the system > and see the same behavior. First, have you read Michael W. Lucas' book (if you haven't already): https://www.michaelwlucas.com/nonfiction/sudo-mastery Secondly, maybe you can add the user to a group so sudo is not needed for your command. Next, are you sure your sudo file doesn't have this uncommented: # %wheel ALL=(ALL) NOPASSWD: ALL > Thank you. > > Martin McCormick -- inum: 883510009027723 sip: jungleboogie@sip2sip.info xmpp: jungle-boogie@jit.si
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53F28C01.8060800>