01-11-2009
Sudo is a cross platform userland command that provides something similar to pfexec with some more features like ability to specify the commands parameters and environment. Authentication is handled differently with sudo.
RBAC is a more secure wider solution tied to the (Solaris) operating system. It provides a much finer control about what can be authorized or forbidden.
10 More Discussions You Might Find Interesting
1. UNIX Desktop Questions & Answers
ehe may i know what are the difference between Unix & Linux, and what are the advantages of having Unix as well as disadvantages of having Unix or if u dun mind i am dumb do pls tell me what are the advantages as well as the disadvantages of having linux as well. thanks (1 Reply)
Discussion started by: cybertechmkteo
1 Replies
2. UNIX for Advanced & Expert Users
Hello,
I am trying to convince my boss to stop allowing our users to login as root (superuser). Currently our users login to our unix server with their own account, then as needed, they will do an su and put in the root password.
This scares me, for a bunch of reasons. Mainly, one is that we... (1 Reply)
Discussion started by: rwallaceisg
1 Replies
3. Linux
Hi all,
What the difference between the sudo users & RBAC when the talk of effects after doing the above comes???
any differences between them ,kindly list ?? (1 Reply)
Discussion started by: saurabh84g
1 Replies
4. Solaris
I'm trying to set up RBAC, and I need to know where the logs for RBAC are.
I'm using Solaris 10 as my OS.
I've been reading a lot of documents online and just can't seem to find where the related logs are.
My problem is I need to be able to track a user when they su to a role profile, and... (2 Replies)
Discussion started by: bitlord
2 Replies
5. Solaris
Dear ALL
please can anyone tell me from where can i install sudo for solaris 8 & 9
and how i can install it in the solaris server . (1 Reply)
Discussion started by: thecobra151
1 Replies
6. Solaris
what is the difference between sudo and pbrun?
i have seen people executing pbrun sudo su - what this means?? i know su -
will try to switch to root user. what speciality pbrun gives to sudo when it is used along with sudo command? (2 Replies)
Discussion started by: chidori
2 Replies
7. UNIX for Dummies Questions & Answers
Hi I just wanted to know the difference between Using Sudo mechanism over using Power breaker utilities.
Are they recommended over sudo?
Why ? (4 Replies)
Discussion started by: pinga123
4 Replies
8. UNIX for Advanced & Expert Users
I have an error when using chdev with sudo as follows;
sudo chdev -l rmt0 -a block_size=512
chdev: 0514-518 Cannot access the CuDv object class in the device
configuration database.
I've added chdev in sudoers but still get the error, I guess it's something to do with CuDv... (3 Replies)
Discussion started by: gefa
3 Replies
9. Shell Programming and Scripting
when the following command is issued the command prompt is received, how do I get past this?
ssh -t usera@hosta sudo su - userb -c id (4 Replies)
Discussion started by: squrcles
4 Replies
10. UNIX for Dummies Questions & Answers
Hi All,
Can anyone please help me understanding what the difference between the below two?
1. script.sh &
2. nohup script.sh & (2 Replies)
Discussion started by: Anupam_Halder
2 Replies
GKSU(1) User Commands GKSU(1)
NAME
gksu - GTK+ frontend for su and sudo
SYNOPSIS
gksu
gksu [-u <user>] [options] <command>
gksudo [-u <user>] [options] <command>
DESCRIPTION
This manual page documents briefly gksu and gksudo
gksu is a frontend to su and gksudo is a frontend to sudo. Their primary purpose is to run graphical commands that need root without the
need to run an X terminal emulator and using su directly.
Notice that all the magic is done by the underlying library, libgksu. Also notice that the library will decide if it should use su or sudo
as backend using the /apps/gksu/sudo-mode gconf key, if you call the gksu command. You can force the backend by using the gksudo command,
or by using the --sudo-mode and --su-mode options.
If no command is given, the gksu program will display a small window that allows you to type in a command to be run, and to select what
user the program should be run as. The other options are disregarded, right now, in this mode.
OPTIONS
--debug, -d
Print information on the screen that might be useful for diagnosing and/or solving problems.
--user <user>, -u <user>
Call <command> as the specified user.
--disable-grab, -g
Disable the "locking" of the keyboard, mouse, and focus done by the program when asking for password.
--prompt, -P
Ask the user if they want to have their keyboard and mouse grabbed before doing so.
--preserve-env, -k
Preserve the current environments, does not set $HOME nor $PATH, for example.
--login, -l
Make this a login shell. Beware this may cause problems with the Xauthority magic. Run xhost to allow the target user to open win-
dows on your display!
--description <description|file>, -D <description|file>
Provide a descriptive name for the command to be used in the default message, making it nicer. You can also provide the absolute
path for a .desktop file. The Name key for will be used in this case.
--message <message>, -m <message>
Replace the standard message shown to ask for password for the argument passed to the option. Only use this if --description does
not suffice.
--print-pass, -p
Ask gksu to print the password to stdout, just like ssh-askpass. Useful to use in scripts with programs that accept receiving the
password on stdin.
--su-mode, -w
Force gksu to use su(1) as its backend for running the programs.
--sudo-mode, -S
Force gksu to use sudo(1) as its backend for running the programs.
SEE ALSO
su(1), sudo(1)
gksu version 2.0.x August 2006 GKSU(1)