On 2020-10-08 16:39, Klemens Nanni wrote:
On Thu, Oct 08, 2020 at 04:23:53PM -0700, Jordan Geoghegan wrote:
This improved error message would have been useful a few months ago where I
had a number of end-users of one of my scripts get confused due to the
cryptic error messages spit out by
On 2020-10-09, Klemens Nanni wrote:
> In case `cmd' and `args' in doas.conf(5) do not match, the generated
> log message is unclear and might be read as if the command executed but
> failed, i.e. returned non-zero:
>
> # cat /etc/doas.conf
> permit nopass kn cmd echo args foo
>
Klemens Nanni wrote:
> The diff does not change behaviour or output for end-users on the
> command line; instead it changes syslog messages which by default are
> only readable by root.
^
That's the key detail for me, as it means no additional information
is being
On Thu, Oct 08, 2020 at 04:23:53PM -0700, Jordan Geoghegan wrote:
> This improved error message would have been useful a few months ago where I
> had a number of end-users of one of my scripts get confused due to the
> cryptic error messages spit out by doas.
The diff does not change behaviour or
Hi Klemens,
I'm not a dev, so I can't give you an OK, but I just wanted to say that
I certainly support this change.
This improved error message would have been useful a few months ago
where I had a number of end-users of one of my scripts get confused due
to the cryptic error messages spit
In case `cmd' and `args' in doas.conf(5) do not match, the generated
log message is unclear and might be read as if the command executed but
failed, i.e. returned non-zero:
# cat /etc/doas.conf
permit nopass kn cmd echo args foo
$ doas echo foo
foo
$ doas
