As even text editors and file managers can cause breakages when spawned with sudo, and this could break permissions or file ownership, among other things. Please be exceptionally careful, nonetheless. While there are still dangers to launching some apps in this regard, as they could also break these things, especially if they're not made with that use case in mind, the dangers are minimized to an extent, as just a consequence of that one app (like a file manager or text editor, etc), rather than every process of the DE. To setup root password, open Linux terminal and execute. Everything spawned under this kind of session belongs to root, which could make things inaccessible for your normal user.Īll of that is a gross oversimplification, but the general gist of it is that the dangers are very, very real, and it's why disallowing root graphical sessions has become standard across most (if not all by now) DEs. To enable the Ubuntu root account, first we need to set up password for the root user. There's also the matter of file ownership and permissions. This comes with a lot of baggage, such as the potential breakage of applications that don't expect that kind of operation, or even allowing applications which misbehave to cause irreversible damage to your system if they modify things they shouldn't. When logged as this user I want the home directory, etc, for this user set up correctly until I log out. The dangers of the desktop session being root are rather high, as this means any and all processes spawned under it (apps, services, etc) are all granted elevated privileges. Let's assume I'm logged in to a terminal session and I would like temporarily work as another non-root user whose password I know without leaving my session.
0 Comments
Leave a Reply. |