SU VS SUDO INSTALL
SU VS SUDO FULL
SU VS SUDO PASSWORD

(if on the command line to avoid adding to history put a space first). There are many ways but this is simplest.

SU VS SUDO PASSWORD

use rsync over SSH etc.įinal note is if you want to generate the password file shadow encrypted string in an automated shell etc try this link for more. If FTP is not as secure maybe don't use it anyway. Only thing different from way back is you can't SSH directly to root. MasterJames Lesson of the day and every day for many things is: old school was always better, changing perfection is normal but it doesn't make it right. Yes you can still su from the ssh login user after removal from the group. Actually to this point it may still be untrue since man crypt shows 'By taking the lowest 7 bits of each of the first eight characters of the key, a 56-bit key is obtained.' may still only use the first 8 chars anyway, my tests say otherwise so maybe that's another good question about password lengths. If you also double up the length of the passwords (for both accounts) other then an obvious guessable plain doubling so say 16 characters then it's pretty secure. (obviously you would preferable not need to prefix with sudo since you su'ed to root). This is probably the cleanest safest feeling way to do it meaning remove a user from the group sudo.

SU VS SUDO FULL

You will see this difference in the prompt path not having changed to the tilde (aka user's home directory) vs full /home/user path of the user that just su'ed so probably less desirable then sudo su or sudo -s anyway.Īctually root still cant use SSH to login directly by default anyway so it is added security if you eventually disable the original login account from sudoers. It is added security to have a different user that has access then the hacker has to guess the username as well as a password, but you can add back root, and disable the sudoers for the still unknown account, which would be more secure with double passwords and an unknown username.Īnd to disable or lock root again passwd -l root

SU VS SUDO INSTALL

It asks for the password of the user you want to be, so only knowing that password it accepts the user substitution.Even though it appears sa for system administrator is no longer included in the ubuntu variant by default (apt install acct), so I guess I mean logically.Īctually I guess I am showing my age with 'sa' but never used it because at the time 'su' was a more direct approach.ĭoing 'su' directly is not possible as you need the root password but the account is disabled by default. The most common use of su is to become root. Su: This command allows the user to run a (new) shell / program as another user. It asks the user for their own password, making possible to authorize users to do tasks allowed only to root without revealing root's password. (the user must be allowed previously in /etc/sudoers). It asks the user for their own password, making possible to authorize users to do tasks allowed only to root without revealing root's password. sudo: executes a command as another user but only if the original user is allowed to do it. Sudo: executes a command as another user but only if the original user is allowed to do it. When mount use this option then the file system doesn't allow set-user-identifier ( setuid) or set-group-identifier ( setgid) bits to take effect. It changes its effective user ID from a privileged value (typically root) to some unprivileged one. Suid: (saved user ID) is used when a program running with elevated privileges needs to temporarily do some unprivileged work. It is needed for tasks that require higher privileges than those which common users have, such as changing their login password.

Setuid: (set user ID upon execution) is a Unix/Linux access rights flag that allow users to run an executable with the permissions of the executable's owner.

Su vs sudo