LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Blogs > bigjohn
User Name
Password

Notices

Rate this Entry

Kubuntu and sudo ???

Posted 07-15-2006 at 08:46 AM by bigjohn

Well I'm really starting to get pissed off with kubuntu and it's use of sudo to run/administrate things.

It would appear that the only way round this issue, is to modify the sudoers file so that only root can do stuff with sudo - which defeats the object of making it work like that i.e. if I still have to use sudo to run/administrate the system, but I've set the sudo to only be used by root, then what the bloody point of having sudo installed other than it's what "they" want in the first place.

The only thing thats stopping me saying "fuck it, I think I'll install gentoo" is that there doesn't seem to be a packages CD available for i686. I'm not confident enough with CLI to be able to get the system installed and then to be able to just find all the GRP packages that I'd need to run my system i.e. I'll have to look to see if theres a list of the GRP packages that are available from the mirrors because I can install them via a net connect and then update/fine tune later, but I can't afford to be without a working system (which is a complete PITA).

Anyhow, thats enough moaning for the moment!

TTFN.
Posted in Uncategorized
Views 1209 Comments 2
« Prev     Main     Next »
Total Comments 2

Comments

  1. Old Comment
    I get irritated the way sudo changes in it's implementation across distros and even versions of one distro.

    I also got annoyed with the apparent lack of root control on Ubuntu and the fact that a port < 1024 was left open at the end of the install. Don't know if that still applies but suggest you use nmap to portscan your Ubuntu installation.

    I regained control of root and I actually prefer to use a specific user for sudo control. This may happen to be root but if you man sudoers you'll be able to find out a lot of info about sudo, including the fact that you can limit access to certain commands via specific users or define groups of users or groups that can do certain tasks.

    The prime example of this is server admin versus web dev. Each user in those groups of users have different needs and can therefore be restricted appropriately in what they can do.

    Set up properly sudo is useful; one point to note is that if you set sudo up to use a user's password rather than the root password and then you effectively give that user root powers via sudo then you have to protect that user's passwd the same way you would the root passwd.

    So I would argue, for the home network, root should be used for root stuff under sudo. You can allow the family to mount cdroms or whatever via specific groups in the sudo file and limit serious activity to the sysadmin there.

    Posted 12-31-1969 at 07:00 PM by bigjohn bigjohn is offline
  2. Old Comment
    The easiest way to get the coveted su root access do a sudo passwd.

    Change the password like any other user.

    Trust me tho it sucks. It doesn't forward your X enviornment like mandriva/mandrake does.

    So you're still stuck doing an su -p if you want to run a text editor like kate.

    Posted 12-31-1969 at 07:00 PM by bigjohn bigjohn is offline
 

  



All times are GMT -5. The time now is 03:48 PM.

Main Menu
Advertisement

My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration