security/doas it's an alternative.Fix already landet in ports yesterday.
Anyway, security/sudo is a bug in itself, so not much of a change IMO.
Yes, I know, thank you.security/doas it's an alternative.
su
and don't need anything else.Anyway, I have always been happy withsu
and don't need anything else.
Speaking about sudo and Christmas, this, even if legit, I think would put you under "naughty" anyway: https://xkcd.com/149/BTW: obligatory xkcd for this: https://xkcd.com/838/
security/doas would be a very nice tool, if it would support the kernel module, that it is backed by in OpenBSD. As far as I understand, that should give it the ability to "remember" for a while, that you raised your priviliges, like security/sudo does. I actually never used doas in it's full functionality on OpenBSD, I just read about it. It's kernel module is missing in the FreeBSD port, or at least was missing, when I used it 1,5 years ago.That's always been the way I do things and have never installed security/sudo or security/doas. If I have something that needs to be done as root I do it as root and feel comfortable and competent in doing so. I'm the only usr on my machina anyway.
su -m root -c 'some command'
a simple su -c some command
is enough Yeah, I have a light case of ' '
laziness #!/bin/sh
# This su wrapper simplifies my 2 most common use cases.
# case 1) with -c and at least one more argument executes su -m root -c 'argument(s)'
# case 2) without arguments executes su -m
# case 3) any other combination of arguments is passed to su unchanged
if [ "$1" == "-c" ] && [ $# -ge 2 ]
then
# case 1
shift
sucommand="/usr/bin/su -m root -c '$@'"
eval `echo $sucommand`
elif [ $# -eq 0 ]
then
# case 2
/usr/bin/su -m
else
# case 3
/usr/bin/su $@
fi
su
is all I've ever used. When I'm done I log out and run browsers and such from my usr account. sudo
group than the root or user password.What I do not get is why some people give all privileges without password to their user and then claim that it is safer.