I installed Ubuntu 12.04 LTS (Precise Pangolin), 64 bit. Nowhere was I asked to set password for root.
I just installed AccuRev SCM software. It was installed under the /root
folder by default. Now I try do something on that folder. I tried with su to switch to root, but I don't know its password.
Should I always use sudo or get the default root password, if any?
How do I create a launcher for software installed inside the /root
directory?
By default, the root account is accessed by sudo.
For a complete discussion in the topic, and information for how to set a root password, see: RootSudo - Community Ubuntu Documentation
With that said, it is extremely unlikely you need to set a root password, I advise you use
Or for graphical applications, use gksu
Password for
root
is not set in Ubuntu which means the root login is disabled by default.The user account created during Ubuntu installation is associated with all sudo capabilities. You could use
sudo
for commands that require root privileges in Ubuntu terminal.However you can enable the root account and set a password for it. To do so use:
Firstly you will be asked for your current user password and after this you will be asked for the new password twice (new and retype password) as your new root password.
For more information see RootSudo - Community Ubuntu Documentation.
By default Ubuntu does not set up a root password and therefore you don't get the ability to log in as root. Instead you are given the ability to perform tasks with superuser privileges using sudo.
I've answered a similar question before.
While you can create a password for the root account allowing you to log in as root with
su
, this isn't the typical "Ubuntu" way of doing things. Instead Ubuntu expects that you will be usingsudo
.Using sudo
Sudo is an alternative to giving people a root password in order to perform superuser duties. In a default Ubuntu install the person who installed the OS is given "sudo" permission by default.
Anybody with "sudo" permission may perform something "as a superuser" by pre-pending
sudo
to their command. For instance, to runapt-get dist-upgrade
as a superuser, you could use:By default, sudo will ask you for your own account password when performing this. This helps security. This is remembered for a few minutes so if you have a few tasks to do with sudo it will only ask you for your password on the first.
You will see the above usage of sudo pretty much anywhere you read a tutorial about Ubuntu on the web. It's an alternative to doing this.
Benefits
With sudo, you choose in advance which users have sudo access. There is no need for them to remember a root password, as they use their own password. If you have multiple users, you can revoke one's superuser access just by removing their sudo permission, without needing to change the root password and notify everyone of a new password. You can even choose which commands a user is allowed to perform using sudo and which commands are forbidden for that user. And lastly, if there is a security breach it can in some cases leave a better audit trail showing which user account was compromised.
Not having a root password makes brute force attacks on the root account impossible: this is relevant if you allow login over SSH. Instead, an attacker would need to know a local account name.
Sudo makes it easier to perform a single command with superuser privileges. With
su
, you permanently drop to a superuser shell which must be exited usingexit
orlogout
. This can lead to people staying in the superuser shell for longer than necessary just because it's more convenient than logging out and in again later.Getting a root shell
With sudo, you still have the option of opening a permanent (interactive) superuser shell with the command:
... and this can still be done without any root password, because
sudo
gives superuser privileges to thesu
command.And similarly, instead of
su -
for a login shell you can usesudo su -
or evensudo -i
.However when doing so you just need to be aware that you are acting as a superuser for every command. It's a good security principle not to stay as a superuser for longer than necessary, just to lessen the possibility of accidentally causing some damage to the system (without it, you can only damage files your user owns).
Just to clarify, you can, if you choose, give the root user a password allowing logins as root, if you specifically want to do things this way instead. I just wanted to let you know about the Ubuntu convention of preferring
sudo
instead and let you know that there is an alternative.While we are at it, If you are trying to log in via ssh into the root account and its giving you back the "Permission Denied" look, even after you having updated the root password multiple times over, remember that apart from updating the root password as others have mentioned, you also have to enable the root ssh login in the ssh server config.
set
do the restart dance
Bamm!!! You're in!
PSst: Btw this is for Ubuntu, YMMV.