On Mon, Apr 04, 2016 at 08:08:19AM +0100, Jason McIntyre wrote:
>
> it is a bit inconsistent, yes.
>
> it is very much less readable with a line break. you could remove the
> offset, but that doesn;t look great either. you could specify a smaller
> offset and juggle the actual text a bit.
>
>
On Mon, Apr 04, 2016 at 12:26:50AM +0200, Tim van der Molen wrote:
> Philip Guenther (2016-04-01 23:47 +0200):
> > Sooo close. To quote doas.conf(5):
> >
> > The rules have the following format:
> >
> >permit|deny [options] identity [as target] [cmd command [args
> > ...]]
>
Philip Guenther (2016-04-01 23:47 +0200):
> Sooo close. To quote doas.conf(5):
>
> The rules have the following format:
>
>permit|deny [options] identity [as target] [cmd command [args ...]]
...
> 'args' is *literal* there, so the correct config line would be
> permit
On Fri, Apr 01, 2016 at 02:47:42PM -0700, Philip Guenther wrote:
[snip]
> Sooo close. To quote doas.conf(5):
>
[snip]
> 'args' is *literal* there, so the correct config line would be
> permit nopass support as root cmd /usr/sbin/rcctl args restart ntpd
>
Hahaha, holy fballs! *donk*
see doas.conf(5):
args ... Arguments to command. If specified, the command arguments
provided by the user need to match for the command to be
successful. Specifying args alone means that command should
be run without any arguments.
On Fri, Apr 1, 2016 at 2:33 PM, Tor Houghton wrote:
> Now that sudo is out of base, I am wondering -- do I need to add it again,
> or does doas.conf allow for specifying commands with arguments?
>
> Obviously not like this (doas doesn't like that), but akin to:
>
> permit
Hi,
Now that sudo is out of base, I am wondering -- do I need to add it again,
or does doas.conf allow for specifying commands with arguments?
Obviously not like this (doas doesn't like that), but akin to:
permit nopass support as root cmd /usr/sbin/rcctl restart ntpd
I don't want the
7 matches
Mail list logo