Showing results for 
Search instead for 
Did you mean: 

sudo need to be configure

Viney Kumar
Regular Advisor

sudo need to be configure


I want to give ALL=ALL (except to su to root) aceess to a group.

Please suggest how can we do this with sudo.

Suraj K Sankari
Honored Contributor

Re: sudo need to be configure


Here is the link where you can know everyting about sudo.

Honored Contributor

Re: sudo need to be configure

ALL commands on ALL hosts, with no limit on target usernames? Then they won't need su for root access: they can easily make their own root shell.

You'll find your users will start using something like:

sudo /usr/bin/csh
# full root access!


cp /usr/bin/ksh $HOME/myrootshell
sudo chown root $HOME/myrootshell
sudo chmod u+s $HOME/myrootshell
# full root access!

or even something like:

sudo more /etc/hosts
!/usr/bin/sh (a shell escape command for "more")
# full root access!

The easiest way would be to limit the allowed target usernames. For example, if your users in group "appadm" must be able to qrun any commands as appuser1 and appuser2, then the sudo configuration could be like this:

User_Alias APPADMINS = %appadm
Runas_Alias APPUSERS = appuser1, appuser2


You must then instruct your users to use commands like:

sudo -u appuser1 -i
to get a shell session as appuser1, or

sudo -u appuser1 somecommand
to run individual commands as a particular user.

Viney Kumar
Regular Advisor

Re: sudo need to be configure

Hi Matti

thanks for reply

There some security risks in your perivious suggesstion

1. when user use /usr/bin/csh,we just get log for first cmd and no log for which user running in csh shell
log output:-

OCT 7 10:06:02 2009 : viney : HOST=bscstest : TTY=pts/0 ; PWD=/home/viney ;
USER=root ; COMMAND=/usr/bin/csh

2. when we using Alias still user can able to su to root that i need to disable

Alias details which im using in sudoers file

User_Alias UNIX=%unixl2
Runas_Alias UNIX_L2=root
UNIX ALL=!/usr/bin/passwd root

Waiting for more suggestion on this
Honored Contributor

Re: sudo need to be configure

1.) Yes. You did not say anything about logging requirements in your original post. If you need logging, google for "sudosh", an utility that can be used along with sudo to provide a complete transcript of each session started through it.

If you don't want the user to execute a shell on the target user account, don't allow them to start a shell through sudo. And don't allow any command that has the function of starting a shell. And don't allow any command that could be used to deconfigure your restrictions either.

If you allow someone to execute commands as root with no restriction to the set of commands allowed, then that person does not need "su" to become root: s/he has an unlimited number of ways to duplicate the effects of "su".

2.) Yes, definitely. If you try to create a sudo policy by allowing "everything except these commands", you will always end up with allowing too much.

The problem is that the basic Unix tools required to install/maintain/troubleshoot/debug an application running as root can also be used to create an unrestricted and un-logged root access to any user.

The only solution to this problem is to not run applications as root so that you don't have to grant ALL=ALL access to people who are not trusted sysadmins.

If you run the applications on separate user accounts dedicated to this purpose, you can then use sudo to grant people access to those application accounts *only* without giving them root access at all.

Let's start over at the beginning.
You have a group named "unixl2" that needs to do something. You think that requires ALL=ALL style access, which includes unrestricted root access. But the members of the group apparently must not be allowed to become root.
What exactly does the "unixl2" group need to do?

Viney Kumar
Regular Advisor

Re: sudo need to be configure

yes matti

exactly i want to do
Occasional Advisor

Re: sudo need to be configure

# sudoers file.
# This file MUST be edited with the 'visudo' command as root.
# See the sudoers man page for the details on how to write a sudoers file.

# Host alias specification

# User alias specification

# Cmnd alias specification

# Defaults specification

# User privilege specification
root ALL=(ALL) ALL

# Uncomment to allow people in group wheel to run all commands
# %wheel ALL=(ALL) ALL

# Same thing without a password

# Samples
# %users ALL=/sbin/mount /cdrom,/sbin/umount /cdrom
# %users localhost=/sbin/shutdown -h now