Why would anyone do that? ![]()
The whole idea of passwords is security.
This is not advisable. DO NOT DO THIS
What he is suggesting is is passwordless sudo for ALL commands. It collapses the boundary between your user account and root. Anything that runs as you, a browser exploit, a bad AUR package, a stray script, gets effortless root with no friction.
![]()
100% agree, @docbrody. I’m quite stunned that anyone would even consider such a potentially dangerous thing. Especially since Arch has been under DDoS attacks for a year or so. Unsafe regardless.
For those who knows what they’re doing and not listen to those who don’t know what they’re doing spout fear.
Geatian 6
What I do is add:
Defaults timestamp_timeout=-1
somewhere in the sudo file. Any new terminal you open you’ll still need to type your password the first time you sudo, but it never expires. Any subsequent sudo use from that terminal session won’t prompt for a password.
Perhaps this is also dangerous; I’ve only been a linux user since last November, but it feels like a reasonable compromise.
Anyone who knows what they are doing, do not need that help. To anyone else, it’s an open door to ruin their system (or worse).
eTux 8
Oooh boy…
![]()
mfq 9
totally agree! security risk.
if you want to use your system without typing everytime the sudo password, just buy a FIDO2 key. That way you can authorize sudo with a finger tap (e.g. yubikey: auth sufficient pam_u2f.so cue)
dennis1 10
Dude, just cherry pick and add commands you know/feel are safe like maybe /usr/bin/pacman -Syu and similar. NOPASSWD:ALL is not the best idea.
IAmHugh 11
Just wrong, so wrong. As @Uncle_Spellbinder said having to enter the password is about security.





























