Sudo to execute script without passwd[solved]

Operating Systems Linux Red Hat Sudo to execute script without passwd[solved]

03-19-2012

Registered User

13, 0

Join Date: Nov 2011

Last Activity: 13 September 2012, 12:19 PM EDT

Posts: 13

Thanks Given: 3

Thanked 0 Times in 0 Posts

Sudo to execute script without passwd[solved]

Hi

Hope someone can sched some light i'm trying to execute a script via sudo but i don't want to be prompted for a password when i run the script using sudo

my sudo entry does work in that the script gets executed but i'm having to give a password, my current entry is given below

user1 host1=NOPASSWD: /user1/source/test.sh

This is on rhel environment

Chers
Duckegg

---------- Post updated at 06:26 AM ---------- Previous update was at 05:39 AM ----------

Got it working by adding spaces between the = sign

duckeggs01

View Public Profile for duckeggs01

Find all posts by duckeggs01

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

How to execute command remotely as sudo and save the output locally?

Hello , I am trying to run a NetBackup command in remote server. Also this command can only be run by root so I am using sudo . Also I want the output of the command locally in a file. The below command asked for password , ran successfully and showed Output on my local server screen ...

2. HP-UX

Sudo entry required to set permission similar to ROOT without using password (PASSWD) change optio

Hi All I had installed sudo in HP UX 11.3 and it is working fine but not able to make entry required to set permission similar to ROOT without using password (PASSWD) change option for define user in /etc/sudoers file Please help if some know the syntex? :confused::wall:

3. UNIX for Dummies Questions & Answers

[Solved]Can anyone tell me why -H flag with sudo doesn't switch to the target user's home directory?

I have checked the man page ,which says : The -H (HOME) option sets the HOME environment variable to the homedir of the target user (root by default) as specified in passwd(5). By default, sudo does not modify HOME But I have tried below command: #...

4. Shell Programming and Scripting

"Cannot Execute" script, SunOS. [solved]

I have a script in Server A that will run a script in ServerB. #!/bin/ksh/ ssh user@server "/path/script.sh" The script permissions are as follow: -rwxrwxrwx 1 user dba 75 Jun 11 10:00 script.sh I checked the existence of 'ksh' in /bin and its there. (bash isnt) ...

5. HP-UX

[solved] HP-UX /etc/passwd file

Hi. i have the accessibility to cat the /et/passwd file in this file we see the paassword field but the password is in encrypted form So, it can be possible to get the password encrypted string to convert it into human readable string via some md5 encryption code mechanism etc.. ...

6. Solaris

[Solved] passwd command not working

Hi all, I have got a problem, i have Solaris 8 server, where on running the passwd command, it says permission denied. I have checked /bin/passwd, /etc/passwd, /etc/shadow all have permissions as like one working server. It is happening for root user and all other users. i have tried...

7. UNIX for Advanced & Expert Users

suid with execute set for passwd

Hello All, We could see that suid with execute is set for passwd: -rwsr-xr-x 1 root root 22960 Jul 17 2006 /usr/bin/passwd that means if any user execute command passwd that will be executed with root priviledge then why a normal user was not able to change other user password any...

8. Shell Programming and Scripting

Issue in passing passwd to login into a sudo account

Hi Gurus, I have small issue... I used to pass the passwd for sudo commands like below, gzcat ~/passwd.gz | sudo su - <villin> >> eof ------ ----- ------ eof And it was able to login into "villin" sudo account successfully. But now, I'm using the same in another script for the...

9. Shell Programming and Scripting

[Solved] how Execute a Perl Script from any location on the machine

hi guys, i have a query, i wrote a perl script that will collect cpu statistics Scripts/myScripts/ cpu.pl i want to make this file so that i can run it from any location on any drive, without giving the path explicitly. like $/home/ravi/perl cpu.pl i tried this...

10. Shell Programming and Scripting

Execute .sh file with sudo in it

Hi, I logged into a UNIX system as user ABC. I do not have root previleges and also do not have root password. I am executing few commands as: ABC****>sudo su - XYZ XYZ****>rm file1.txt XYZ****>exit ABC****> Now I want to execute all these commands from a .sh file ( or in any other...

LEARN ABOUT REDHAT

visudo

visudo(8)						       MAINTENANCE COMMANDS							 visudo(8)

NAME

       visudo - edit the sudoers file

SYNOPSIS

       visudo [ -c ] [ -f sudoers ] [ -q ] [ -s ] [ -V ]

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 vari-
       able.  This list defaults to the path to vi(1) on your system, as determined by the configure script.  Normally, visudo does not honor the
       EDITOR or VISUAL environment variables unless they contain an editor in the aforementioned editors list.  However, if visudo is configured
       with the --with-enveditor flag or the enveditor Default variable is set in sudoers, visudo will use any the editor defines by EDITOR or
       VISUAL.	Note that this can be a security hole since it allows the user to execute any program they wish simply by setting EDITOR or VIS-
       UAL.

       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  Specify and alternate sudoers file location.  With this option visudo will edit (or check) the sudoers file of your choice, instead of
	   the default, @sysconfdir@/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
	   flag.

       -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.

ERRORS

       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: undeclared Alias referenced near ...
	   Either you are using a {User,Runas,Host,Cmnd}_Alias before defining it or you have a user or hostname listed that consists solely of
	   uppercase letters, digits, and the underscore ('_') character.  If the latter, you can ignore the warnings (sudo will not complain).
	   In -s (strict) mode these are errors, not warnings.

ENVIRONMENT

       The following environment variables are used only if visudo was configured with the --with-env-editor option:

	EDITOR		       Invoked by visudo as the editor to use
	VISUAL		       Used Invoked visudo if EDITOR is not set

FILES

	/etc/sudoers	       List of who can run what
	/etc/sudoers.tmp       Lock file for visudo

AUTHOR

       Many people have worked on sudo over the years; this version of visudo was written by:

	Todd Miller	       <Todd.Miller@courtesan.com>

       See the HISTORY file in the sudo distribution or visit http://www.sudo.ws/sudo/history.html for more details.

BUGS

       If you feel you have found a bug in sudo, please submit a bug report at http://www.sudo.ws/sudo/bugs/

DISCLAIMER

       Visudo is provided ``AS IS'' and any express or implied warranties, including, but not limited to, the implied warranties of merchantabil-
       ity and fitness for a particular purpose are disclaimed.  See the LICENSE file distributed with sudo for complete 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.

SEE ALSO

       vi(1), sudo(8), vipw(8).

3rd Berkeley Distribution					       1.6.6								 visudo(8)

Red Hat