Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
HOWTO - get kdesu back to normal in KDE4 - http://forums.debian.net/viewtopic.php?f=16&t=40158
This one is actually pretty easy. In a terminal here is what you do:
Anywhere you see ## just after that is instructions you do NOT have to type the text directly AFTER the ## signs,
what you have to type will either be BEFORE the ## on a line or the line will have NO ## signs.
##first type in:
su
##after you hit enter you will see
Password: ##<----------- type in your root password here.
##Now you will see your prompt change from a $ to a # sign
##Don't worry, almost done now...
##type:
ln -s /usr/lib/kde4/libexec/kdesu /usr/bin/kdesu
##hit enter, then type:
exit
##You are now back to your regular user in your terminal. Lets test that puppy out!
kdesu dolphin
##The normal kdesu dialog should pop up asking for roots password with the explanation that the program
##dolphin needs root permissions. You can just cancel the dialog box since it was only a test to see if the link
##worked.
Raspberry PI 400 Distro: Raspberry Pi OS Base: Debian Sid Kernel: 5.15.69-v8+ aarch64 DE: MATE Ram 4GB Debian - "If you can't apt install something, it isn't useful or doesn't exist" My Giant Sources.list
I have exactly two apps installed that use sudo, apper and PeerGuardian. Other than that I never use sudo, I use either kdesu or su.
But many new user coming from other distros especially the *buntus are used to using sudo, hence the howto.
Raspberry PI 400 Distro: Raspberry Pi OS Base: Debian Sid Kernel: 5.15.69-v8+ aarch64 DE: MATE Ram 4GB Debian - "If you can't apt install something, it isn't useful or doesn't exist" My Giant Sources.list
There is another how-to in the how-to-section, a bit old: http://forums.debian.net/viewtopic.php?f=16&t=45390
As i don't use sudo i can't say if it is further info or just superfluous chat by me.
If the latter: ignore.
craigevil wrote:But many new user coming from other distros especially the *buntus are used to using sudo, hence the howto.
IOW, so they can keep on sticking to a bad habit they're just used to?
Although new users who have taken the trouble to read Debian documentation on the subject may be excused for sticking to the habit having read that it is common practice: debian-reference/ch01.en.html#_sudo_configuration
For the typical single user workstation such as the desktop Debian system on the laptop PC, it is common to deploy simple configuration of sudo
Or may consider it better (safer) for the reasons given here: wiki.debian.org/sudo:
Using sudo is better (safer) than opening a session as root for a number of reasons...
kedaha wrote:Or may consider it better (safer) for the reasons given here: wiki.debian.org/sudo:
Using sudo is better (safer) than opening a session as root for a number of reasons...
This applies to the scenario of sudo vs running an x session as the root user - in such a case sudo is obviously infinitely safer and the better practice.
craigevil wrote:But many new user coming from other distros especially the *buntus are used to using sudo, hence the howto.
IOW, so they can keep on sticking to a bad habit they're just used to?
Although new users who have taken the trouble to read Debian documentation on the subject may be excused for sticking to the habit having read that it is common practice: debian-reference/ch01.en.html#_sudo_configuration
For the typical single user workstation such as the desktop Debian system on the laptop PC, it is common to deploy simple configuration of sudo
Well, lo and behold, shoot me in the head.
kedaha wrote:Or may consider it better (safer) for the reasons given here: wiki.debian.org/sudo:
Using sudo is better (safer) than opening a session as root for a number of reasons...
And here are the reasons listed:
http://wiki.debian.org/sudo wrote:
Nobody needs to know the root password (sudo prompts for the current user's password). Extra privileges can be granted to individual users temporarily, and then taken away without the need for a password change.
It's obvious that one needs to know root passwd, especially on a single-user system.
http://wiki.debian.org/sudo wrote:
It's easy to run only the commands that require special privileges via sudo; the rest of the time, you work as an unprivileged user, which reduces the damage that mistakes can cause.
Unless you're in the habit of spamming sudo in front of various commands. Just in case. Nothing can be done when PEBCAK.
http://wiki.debian.org/sudo wrote:
Auditing/logging: when a sudo command is executed, the original username and the command are logged.
When using su, the commands get logged in root's $SHELL history. Again, especially in a single-user install, what's the point? <-- Rhetorically, that is. I guess it's a case of YMMV again.
Q: Why is the Eunux kernel so bloated?
A: It was made in the image of its founder.
kedaha wrote:Or may consider it better (safer) for the reasons given here: wiki.debian.org/sudo:
Using sudo is better (safer) than opening a session as root for a number of reasons...
And here are the reasons listed:
http://wiki.debian.org/sudo wrote:
Nobody needs to know the root password (sudo prompts for the current user's password). Extra privileges can be granted to individual users temporarily, and then taken away without the need for a password change.
It's obvious that one needs to know root passwd, especially on a single-user system.
If it is a self-administered system, I agree with you. But I certainly don't think, for example, a secretary using a workstation for secretarial work in an office needs to know the root password, or anyone else for that matter including the boss.
http://wiki.debian.org/sudo wrote:
Nobody needs to know the root password (sudo prompts for the current user's password). Extra privileges can be granted to individual users temporarily, and then taken away without the need for a password change.
It's obvious that one needs to know root passwd, especially on a single-user system.
If it is a self-administered system, I agree with you. But I certainly don't think, for example, a secretary using a workstation for secretarial work in an office needs to know the root password, or anyone else for that matter including the boss.
Agreed. If it's a multi-user environment, sudo has its uses, in its restricted, proper way of usage. That is, notusername ALL=(ALL:ALL) ALL style, which would be a quick road to disaster.
Q: Why is the Eunux kernel so bloated?
A: It was made in the image of its founder.
kedaha wrote:If it is a self-administered system, I agree with you. But I certainly don't think, for example, a secretary using a workstation for secretarial work in an office needs to know the root password, or anyone else for that matter including the boss.
Does a secretary using a workstation need any kind of root access, whether it's a root password or sudo...?
debil wrote:Agreed. If it's a multi-user environment, sudo has its uses, in its restricted, proper way of usage. That is, notusername ALL=(ALL:ALL) ALL style, which would be a quick road to disaster.
yes that's my main gripe with sudo - its NEVER configured properly to allow only certain users to run certain commands.
without that being done (i.e. n00buntu default) its hideously insecure and prone to PEBKAC errors. n00buntu seem to do it purely to stop people logging into X as root.