When I first installed Etch I managed to allow for root to log in at startup. Somehow the system has since changed that back, an now I've searched virtually the whole computer and can't find the screen with the checkbox. If anyone could help with this I would be so greatful, since I love to have a separate root desk.

Also, when playing music in Juk and fiddling with the windows (moving, stuff like that) there is this squeeking noice in speakers. Does someone know how to get rid of it? It's just downright annoying.

I'm on a Compaq Intel PIII
Win + Etch (not single-user)
Sounblaster live! soundcard
256 MB

Thanks
Tillus

This worked on my Ubuntu box; I was able to get a graphical root log-in. Not sure if it'll work in Debian.

sudo passwd

where did you print that?

I tried the login, but that failed. Also tried terminal, didn't work either.

Try this: Desktop (menu, top) -> Administration -> Login Window (enter root pw) then select the Security tab. Check the "Allow local administration login"

From what I understand of the question he wants to log on to an X session as root.

We can try to make him understand the dangers and explain that it is better to use su and sudo, but do you think he'll listen?

Probably not, but don't let that stop you from trying. Besides, I don't think it's possible from KDE anyway. The only settings dialog for the login window I can find is for gdm.

Also, if anyone knows how to get rid of that shreeking noise, especially when streaming.

It *is* possible in KDE, but as I have said above I very strongly urge you to reconsider. Why do you think windows users are hit so often and so hard?

It is because on windows, by default, you run as administrator, giving *every* program full access to everything. This is basically what you do when you run your X-session as root. Every glitch in the program, every exploit in the program, buffer overflow etc means the misbehaving piece of software can do *anything* with your system.

Also, running as a user protects us from ourselves. And please don't give me the excuse that you never mess up. Ok, wait, let's for a moment assume you never mess up ok... now you are typing the command rf -r ./ for instance, but the dot on the keyboard is sticky and didn't register your keypress. you press enter and you have just told your OS to remove EVERYTHING from EVERY partition and device mounted. Pretty scary huh?

I am a system administrator and sofware developer. I have much experience with Linux and I tell you: I run my X-Session as a user, ALWAYS. when I need to do something that requires root privileges, either there is the pam module that pops up and asks me for the root password, or on the console I use su, not sudo because su always requires you to enter the root password.

I strongly believe that it is your duty as Linux user to run as a user. If we all run as root then I can pretty much guarantee you that we will be experiencing a very high amount of malware targeted to us.

If you are still not convinced, then I challenge you to give me a valid reason to run your desktop as root.

Tillus,

Debian removes the capability of logging in to KDE as root. That is for safety. You can run individual programs as root by choosing "Run..." from the KDE menu and run as a different user.

Command line programs you can run from within a terminal and entering the "su" command.

There is really, really, really no reason to log in to KDE as root, and it is fairly dangerous.

jlinkels

Agreed. You don't need to log-in as root. If you need to administer your system then just invoke su to get a root terminal. For example as a regular user you can edit, save your sources.list.

#nano /etc/apt/sources.list

I admire the way that Debian functions:-)

Hitest,

Unfortunately my editing took a long time, and my post was after x_terminator_or_3. His post made mine redundant, but I didn't see that.

About sources.list, no you canNOT edit it as a regular user:
You'd have to chmod the file. For a single (personal) machine that is fully acceptable though.

jlinkels

True, but even then I advocate the use of the su command to invoke an editor with root-access. Yes, even gedit has root-access when invoked from the root-cli So does nano... So: no need to chmod any config files to edit them as a regular user.

@Tillus: as a new Linux user you should familiarize yourself with the way Linux works, 'cause it differs fundamentally from any Win-OS. Read some books and howtos about Linux, either online or on paper.

You can not invoke a root shell as a regular user and edit the file? I just tried it and it works fine.

Tillus

Because I know you have all your data backed up, and your operating system(s) also, who cares what can happen when logged into X as root when you have no fear. Check post #3 in this thread.

Hehehe, now I read that page the link points to, it reminds me of that other OS. Whenever I need to do something as administrator, I have to log off as current user (writing 400MB of roaming profile), log in as administrator (load 30 MB of profile), do the admin job, log off (write 30 MB profile) and log in as user again (and load 400 MB roaming profile) and check if worked what I just tried. Usually not, and it would not be the first time that I keep switching between user and administrator for an entire morning.

Some people simply choose for convenience

jlinkels

The problem is not only the problem HE can create in running as root. The most important is that somebody who can take control of a buggy software (kde,gnome,firefox as least) will have _full access_ to his box.
I'm currently able to crash kde and gnome in a few clicks. If it turns out that this is exploitable to execute some code, then this code will run as root and will be able to install, say a rootkit that can remain undetected for months, unless the person has a strong knowledge on this OS.

Security concept #1 is: Run with least priviledge. It's common sense... The higher you jump the more harm you make when you fall..

If you run your complete WM as root, you don't understand anything about security.
The only case where it's maybe not a problem is with an unconnected machine and nobody plugs anything into it AND you are sure you will never make a mistake (which is false)

But anyway, can you answer this question:

People here are ready to help you to administer the machine without loggin in as root so ask for a specific reason to run WM as root.