Great work Donald ! I especially liked how you explain "why sudo" by referring to enterprise needs. I started few weeks ago a RUclips channel on Linux/Basic Bash usage, and I took the liberty to "feature" your channel -- as your content will definitely interest my viewers. I hope you're OK with that -- otherwise, don't hesitate to let me know.
when I tried to analyze /var/log/auth.log for a sudo privileged user on my Debian machine I get the same output for the root : session opened- session closed . no user activities is logged . so am i missing something here ?
It's hard to say without seeing what you're doing, and without seeing the logfile. My best guess though, is that the sudo user might must be logging into a root command prompt with "sudo su" or "sudo su -", instead of doing individual "sudo" commands from his normal command prompt. If you want to see everything that a user does with root privileges, then you'll need to take away his ability to go to the root command prompt.
Great work Donald ! I especially liked how you explain "why sudo" by referring to enterprise needs.
I started few weeks ago a RUclips channel on Linux/Basic Bash usage, and I took the liberty to "feature" your channel -- as your content will definitely interest my viewers. I hope you're OK with that -- otherwise, don't hesitate to let me know.
Are you kidding? I love it when people advertise for me! ;)
I should also say, "Many thanks!"
Completely a beginners on these stuffs, thanks for sharing your knowledge.
however, keep in mind: passwordless sudo can bring a serious breach to system-wide security.
Very true, and I don't recommend doing it.
why to use sudo for passwd??????
You are the best
Live Examples will be more helpful for beginners
when I tried to analyze /var/log/auth.log for a sudo privileged user on my Debian machine I get the same output for the root : session opened- session closed . no user activities is logged . so am i missing something here ?
It's hard to say without seeing what you're doing, and without seeing the logfile. My best guess though, is that the sudo user might must be logging into a root command prompt with "sudo su" or "sudo su -", instead of doing individual "sudo" commands from his normal command prompt.
If you want to see everything that a user does with root privileges, then you'll need to take away his ability to go to the root command prompt.
linux is too complicated
they should replace sudo with rootapt install to installapt remove to removeuname to aboutand etc