Yes, this is why I made a disclaimer about doing this. It isn't secure, much like disabling UAC in windows isn't secure. However, I do it for convenience at home and would never do that in a work environment.
Hey Chris, an experienced user can edit sudoers with any editor but, as for the beginners, the recommended and safer way to edit sudoers is via: sudo visudo. This will prevent them from commiting syntax errors because if you put a single comma in a wrong place, you can break sudo and then they are going to have troubles restoring it.
Good tip and advice. Thanks. When I would do server admin I normally would ssh in as root (using private key always). I'd very rarely login as non-root account. On desktop in home environment will use your tip because installing packages and entering PW is a PIA everytime! Also if somebody does install as root and can't access as user they can always chown the file/folder.
Thanks for the help! I've saved the link to this video in my browser. I started using computers in the DOS days, so Terminal is familiar to me. Even some of the commands are the same; just the modifiers are different.
Do you mean you have to type your sudo pswd *every* time you used it? because if I have a terminal window that I typed the sudo password in, even if use sudo again it won't prompt me for a pswd for at least 15-25mins. In that terminal window.
@Chris Titus Tech OK I have a question for you. In an enterprise environment, how do i manage user sudo rights from a Windows Active Directory? I'm guessing that I need to set X commands to only be run by DOMAIN group, then add users to that group from ADUC. is that the best way to do this? editing SUDO directly for each user on each box is cool if you only have 3 boxes. but if you have 50 boxes......... o my.
When I even type ''sudo su'' I always get to the point where I have to type my password in. When I type it in the correct way it says ''(my username) is not in sudoers file. This incident will be reported.'' Like, what do I actually do as I am new to linux. Even if I run your command ''sudo nano /ect/sudoers'' I still get the same thing when I type in my password.
Good video, but for me, thanks, but no thanks. I'd rather type it in 20k times, the benefits are big for the effort that is comparatively small. I suppose changing that with a script in Path and forcing a script to return to default on boot is a valid solution. Requiring you to compromise your security only while installing packages.
@@mbk0mbk I think if a hacker is able to get access to your PC in the first place that is a major security concern. Personally, anything I keep directly on my PC that has personal information is encrypted and even if it was stolen, good luck trying to decrypt it. Also, I don't keep things like tax returns and very sensitive spun up on live media all the time. I bounce around a bunch between work and home, so I make it a point that I can pretty much wipe out any PC and not have to worry about it.
@@mbk0mbk For this I'd recommend a security conscience distribution, like TAILS. Password on BIOS, eliminate GRUB screen to prevent root password reset, and full drive encryption. That is for the tinfoil hat people out there, bank system administrators, and folks with more sinister intentions. I don't fit any of that criteria so I won't be doing this anytime soon 😀
change user not to use password for sudo things AT ALL ? :0
Yes, this is why I made a disclaimer about doing this. It isn't secure, much like disabling UAC in windows isn't secure. However, I do it for convenience at home and would never do that in a work environment.
@@ChrisTitusTech I have probably mislistened.. True enough
Hey Chris, an experienced user can edit sudoers with any editor but, as for the beginners, the recommended and safer way to edit sudoers is via: sudo visudo. This will prevent them from commiting syntax errors because if you put a single comma in a wrong place, you can break sudo and then they are going to have troubles restoring it.
Good tip and advice. Thanks. When I would do server admin I normally would ssh in as root (using private key always). I'd very rarely login as non-root account. On desktop in home environment will use your tip because installing packages and entering PW is a PIA everytime! Also if somebody does install as root and can't access as user they can always chown the file/folder.
Thanks for the help! I've saved the link to this video in my browser. I started using computers in the DOS days, so Terminal is familiar to me. Even some of the commands are the same; just the modifiers are different.
Thank you Chris, I use this today . I have a new PC and I install Debian 10 (Buster) stable fresh :)
this guy is so helpful to new linux users. what a nice guy. not a pretentious linux deuche
Bro, how have you got PhotoShop on there? Is that WINE or something else?
Do you mean you have to type your sudo pswd *every* time you used it? because if I have a terminal window that I typed the sudo password in, even if use sudo again it won't prompt me for a pswd for at least 15-25mins. In that terminal window.
@Chris Titus Tech OK I have a question for you. In an enterprise environment, how do i manage user sudo rights from a Windows Active Directory? I'm guessing that I need to set X commands to only be run by DOMAIN group, then add users to that group from ADUC. is that the best way to do this? editing SUDO directly for each user on each box is cool if you only have 3 boxes. but if you have 50 boxes......... o my.
In der Beschreibung wird deutsch geschrieben und dann ist das komplette Video auf Englisch, was soll der Mist
das ist ein youtube feature du vogel
When I even type ''sudo su'' I always get to the point where I have to type my password in. When I type it in the correct way it says ''(my username) is not in sudoers file. This incident will be reported.'' Like, what do I actually do as I am new to linux. Even if I run your command ''sudo nano /ect/sudoers'' I still get the same thing when I type in my password.
Love this intro music man, you have a link?
HO LEE CHIT! YOU DA MAN!... er... YOU DAEMON!
Good video, but for me, thanks, but no thanks. I'd rather type it in 20k times, the benefits are big for the effort that is comparatively small. I suppose changing that with a script in Path and forcing a script to return to default on boot is a valid solution. Requiring you to compromise your security only while installing packages.
I am tempted to do it more. Cuz I am g-root.!!!
What is the meaning of sudo -u oracle -i?
How you highlight commands like "ALL" to red color?
Thx for the advice!!
What about without sudo?
Thank you this really helped me. That was fast and easy.
Nice concise explaination.
thank you. Good explanation
Wow anyone doesn't need to hack your PC just login and run and exploit with sudo.
Yup, I would never do this in a business environment. However for a Home Desktop Environment, I don't mind sacrificing security for the convenience.
@@ChrisTitusTech yeh you said that in video but what if someone wipe your drive or steal the personal files. No hard feeling btw just curious.
@@mbk0mbk I think if a hacker is able to get access to your PC in the first place that is a major security concern. Personally, anything I keep directly on my PC that has personal information is encrypted and even if it was stolen, good luck trying to decrypt it. Also, I don't keep things like tax returns and very sensitive spun up on live media all the time. I bounce around a bunch between work and home, so I make it a point that I can pretty much wipe out any PC and not have to worry about it.
@@ChrisTitusTech ok that's nice . What will you suggest if someone wants to lock down the PC from BIOS, bootloader to DISK itself?
@@mbk0mbk For this I'd recommend a security conscience distribution, like TAILS. Password on BIOS, eliminate GRUB screen to prevent root password reset, and full drive encryption. That is for the tinfoil hat people out there, bank system administrators, and folks with more sinister intentions. I don't fit any of that criteria so I won't be doing this anytime soon 😀