Re: sudoers documentation bug?

2015-06-07 Thread Max Fillinger
On Sat, Jun 06, 2015 at 10:42:16PM +0200, Max Fillinger wrote: Then user can do sudo echo test, but sudo -l prints (root) /bin/echo te st. Sorry, I was talking nonsense here. Line continuation is treated as a space in the sense that it seperates two arguments, so the output of sudo -l is

Re: sudoers documentation bug?

2015-06-07 Thread Todd C. Miller
It is far too late in the game to change this behavior as you will break people's working sudoers files. - todd

Re: sudoers documentation bug?

2015-06-07 Thread Otto Moerbeek
On Sun, Jun 07, 2015 at 07:20:39AM +0900, Joel Rees wrote: Okay, I took the bait. You need to to test for 1 in two places to avoid an out of bounds read (even when just experimenting ;-) tech@ is a better place for this, I don't think millert reads misc@ -Otto On Sat, Jun 6,

Re: sudoers documentation bug?

2015-06-06 Thread Joel Rees
I'm not sure what your question is, or even if you have one. On Fri, Jun 5, 2015 at 6:58 PM, ertetlen barmok ertetlenbar...@safe-mail.net wrote: Hello! http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man5/sudoers.5?query=sudoers Long lines can be continued with a backslash (‘\’) as

Re: sudoers documentation bug?

2015-06-06 Thread Joel Rees
Okay, I took the bait. On Sat, Jun 6, 2015 at 6:29 PM, Joel Rees joel.r...@gmail.com wrote: I'm not sure what your question is, or even if you have one. On Fri, Jun 5, 2015 at 6:58 PM, ertetlen barmok ertetlenbar...@safe-mail.net wrote: Hello!

Re: sudoers documentation bug?

2015-06-06 Thread Max Fillinger
On Sat, Jun 06, 2015 at 06:29:39PM +0900, Joel Rees wrote: I'm not sure what your question is, or even if you have one. I think I figured out what the problem is. Let's say you put the following into your sudoers file: userALL= /bin/echo te\ st Then user can do sudo echo test, but