tedu wrote:
> If you'd like to try current, it should work better for you.
Confirmed working as expected; thanks for the assistance.
Hopefully someone else will benefit from this change as well.
--avj
Adam Jeanguenat wrote:
> tedu wrote:
> > doas allows PATH to be inherited, but resets it for itself to a
> > limited set. this was so that e.g., "permit :wheel cmd ls" can't
> > be tricked by creating a symlink ls -> /bin/sh. however, if there
> > are no restrictions on the command, then the restri
tedu wrote:
> doas allows PATH to be inherited, but resets it for itself to a
> limited set. this was so that e.g., "permit :wheel cmd ls" can't
> be tricked by creating a symlink ls -> /bin/sh. however, if there
> are no restrictions on the command, then the restriction probably
> doesn't need to
Adam Jeanguenat wrote:
> I'm not sure where I'm going wrong here, but I've been giving doas(1)
> a whirl and ran into something that's left be a bit puzzled.
>
> I have some scripts in ~/bin, and my user account has PATH set
> as desired. I can run things out of that dir as expected without
> invo
4 matches
Mail list logo
