10 More Discussions You Might Find Interesting
1. UNIX and Linux Applications
Hello :)
we use LDAP with sudoers about 4 years. Works fine. But we have one problem with members of the admingroup (wheel). This users can do every command with sudo and with there privat password. But when they also are member to another special group, like sysadmin:
Sysadmin is allowed to... (0 Replies)
Discussion started by: darktux
0 Replies
2. Red Hat
All,
I need to disable "sudo -i" and "su - " for all servers in our environment, We want to make sure no one run commands or delete files across environment using switching to root account. can you guys please lets me know if this is achievable.
Thanks and Regards
shekar (2 Replies)
Discussion started by: shekar777
2 Replies
3. Programming
Hi,
I need to somehow pipe the password to a command and run some SQL, for example, something like echo $password | sqlplus -s system @query01.sql
To make it not so obvious, I decided to try out writing a small C program that basically just do echo $password. So now I just do x9.out | sqlplus... (8 Replies)
Discussion started by: newbie_01
8 Replies
4. Solaris
I'm looking for some suggestions to accomplish what a specific user needs, without adding them to the "sudoers" group. I have X user, that is requesting to be able to change file permissions on items owned by others and search directories where X user doesn't have access. I'm open to any... (2 Replies)
Discussion started by: Nvizn
2 Replies
5. Programming
Is there a way to transfer my sudo password via ssh so that I can copy files remotely and pass them locally, so:
cat sudo-passwd-file|ssh -t user@10.7.0.180 'sudo find / -depth|cpio -oacv|gzip' > /path/to/dir/file.cpio.gz
I am in the process of a creating a script. Everytime I try and just... (16 Replies)
Discussion started by: metallica1973
16 Replies
6. HP-UX
Dear folks.
Considering PCIDSS standards, i have requirment to use sudo(ers) to log everything a certain user executes with root privileges.
Now, for an admin it's just a pain in the ass to prefix every command with sudo.
Only way i can think of is making .aliases and with some awk magic... (6 Replies)
Discussion started by: Peasant
6 Replies
7. UNIX for Dummies Questions & Answers
I am trying to write a script that mounts a network drive. The network drive must be as secure and hidden as possible, including being hidden from commands such as df, etc. Any suggestions? (4 Replies)
Discussion started by: CBarraford
4 Replies
8. Solaris
Hi,
on solaris 10, I have two users : user1 and user2
I want to create User_Alias and Cmnd_Alias to allow them to execute a command without prompting for sudo password.
command I want these users should be able to run is '/usr/bin/su - abcd' . Also user1 and 2 need not type the 'abcd'... (6 Replies)
Discussion started by: upengan78
6 Replies
9. Shell Programming and Scripting
I am writing a tool that connects using SSH to a remote server and perform some actions (through root)
However - I would like to hide my operations so they will be hard to track.
I tried STRACE on the SSHD process and saw all the traffic going there so I am quite transparent to STRACE
... (1 Reply)
Discussion started by: yamsin789
1 Replies
10. Solaris
Hi all,
Please help me how to configure the sudo for users and access for perticular
commands,groups ....etc.,
This help really appriciated
regards
Krishna (2 Replies)
Discussion started by: krishna176
2 Replies
VISUDO(8) MAINTENANCE COMMANDS VISUDO(8)
NAME
visudo - edit the sudoers file
SYNOPSIS
visudo [-c] [-q] [-s] [-V] [-f sudoers]
DESCRIPTION
visudo edits the sudoers file in a safe fashion, analogous to vipw(8). visudo locks the sudoers file against multiple simultaneous edits,
provides basic sanity checks, and checks for parse errors. If the sudoers file is currently being edited you will receive a message to try
again later.
There is a hard-coded list of editors that visudo will use set at compile-time that may be overridden via the editor sudoers Default
variable. This list defaults to the path to vi(1) on your system, as determined by the configure script. Normally, visudo does not honor
the VISUAL or EDITOR environment variables unless they contain an editor in the aforementioned editors list. However, if visudo is
configured with the --with-enveditor option or the env_editor Default variable is set in sudoers, visudo will use any the editor defines by
VISUAL or EDITOR. Note that this can be a security hole since it allows the user to execute any program they wish simply by setting VISUAL
or EDITOR.
visudo parses the sudoers file after the edit and will not save the changes if there is a syntax error. Upon finding an error, visudo will
print a message stating the line number(s) where the error occurred and the user will receive the "What now?" prompt. At this point the
user may enter "e" to re-edit the sudoers file, "x" to exit without saving the changes, or "Q" to quit and save changes. The "Q" option
should be used with extreme care because if visudo believes there to be a parse error, so will sudo and no one will be able to sudo again
until the error is fixed. If "e" is typed to edit the sudoers file after a parse error has been detected, the cursor will be placed on
the line where the error occurred (if the editor supports this feature).
OPTIONS
visudo accepts the following command line options:
-c Enable check-only mode. The existing sudoers file will be checked for syntax and a message will be printed to the standard
output detailing the status of sudoers. If the syntax check completes successfully, visudo will exit with a value of 0. If a
syntax error is encountered, visudo will exit with a value of 1.
-f sudoers Specify and alternate sudoers file location. With this option visudo will edit (or check) the sudoers file of your choice,
instead of the default, /etc/sudoers. The lock file used is the specified sudoers file with ".tmp" appended to it.
-q Enable quiet mode. In this mode details about syntax errors are not printed. This option is only useful when combined with
the -c option.
-s Enable strict checking of the sudoers file. If an alias is used before it is defined, visudo will consider this a parse error.
Note that it is not possible to differentiate between an alias and a hostname or username that consists solely of uppercase
letters, digits, and the underscore ('_') character.
-V The -V (version) option causes visudo to print its version number and exit.
ENVIRONMENT
The following environment variables may be consulted depending on the value of the editor and env_editor sudoers variables:
VISUAL Invoked by visudo as the editor to use
EDITOR Used by visudo if VISUAL is not set
FILES
/etc/sudoers List of who can run what
/etc/sudoers.tmp Lock file for visudo
DIAGNOSTICS
sudoers file busy, try again later.
Someone else is currently editing the sudoers file.
/etc/sudoers.tmp: Permission denied
You didn't run visudo as root.
Can't find you in the passwd database
Your userid does not appear in the system passwd file.
Warning: {User,Runas,Host,Cmnd}_Alias referenced but not defined
Either you are trying to use an undeclare {User,Runas,Host,Cmnd}_Alias or you have a user or hostname listed that consists solely of
uppercase letters, digits, and the underscore ('_') character. In the latter case, you can ignore the warnings (sudo will not
complain). In -s (strict) mode these are errors, not warnings.
Warning: unused {User,Runas,Host,Cmnd}_Alias
The specified {User,Runas,Host,Cmnd}_Alias was defined but never used. You may wish to comment out or remove the unused alias. In -s
(strict) mode this is an error, not a warning.
SEE ALSO
vi(1), sudoers(5), sudo(8), vipw(8)
AUTHOR
Many people have worked on sudo over the years; this version of visudo was written by:
Todd Miller
See the HISTORY file in the sudo distribution or visit http://www.sudo.ws/sudo/history.html for more details.
CAVEATS
There is no easy way to prevent a user from gaining a root shell if the editor used by visudo allows shell escapes.
BUGS
If you feel you have found a bug in visudo, please submit a bug report at http://www.sudo.ws/sudo/bugs/
SUPPORT
Limited free support is available via the sudo-users mailing list, see http://www.sudo.ws/mailman/listinfo/sudo-users to subscribe or
search the archives.
DISCLAIMER
visudo is provided ``AS IS'' and any express or implied warranties, including, but not limited to, the implied warranties of
merchantability and fitness for a particular purpose are disclaimed. See the LICENSE file distributed with sudo or
http://www.sudo.ws/sudo/license.html for complete details.
1.7.2p7 June 1, 2010 VISUDO(8)