Article Summary: This article explains the need for sudo without a password, i.e., situations where it is needed. ways to do it. and a recommendation for ease.
Article Description: This is for users who don’t want to enter a password for sudo every time they need it. Bash provides ease for this. It makes this possible for some time after you hit a sudo password for the command the first time. But this is not enough for users who use it very much. So here, you’ll find how to do it for you as well as permanently for your system. Also, safety instructions for doing this.
Need for this comes when you do automate tasks where sudo is necessary.
+1 for this article…
with the expectation that your safety instructions indicate that this can be a loaded gun pointed at your foot, under the wrong conditions.
I’m hesitant on this one. I’m sure it would get a lot of heat from people pointing out that it opens your system up to (easier) intrusion by malware. There is supposed to be a barrier between unprivileged and privileged processes. Is sudo -i not sufficient? For automated processes (cron jobs?) can you not create those under the root account?
Also, if you really want to do an article about sudo, I’d recommend instead writing about the newer run0 command that comes with systemd.
OK. Let us know when/if you get around to researching how to do it with run0 and then I think you might have a good article for Fedora Magazine. Thanks!
