Login or Register to Ask a Question and Join Our Community


UNIX for Dummies Questions & Answers

Problems with Alias, /bin/sh and sudo

 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers Problems with Alias, /bin/sh and sudo
# 1  
Old 05-29-2008
Problems with Alias, /bin/sh and sudo
'exec /bin/sh' breaks alias

--------------------------------------------------------------------------------

I have an application that requires su to root in order to run some commands. Unfortunately, my corporate policy only allows sudo so I created an alias in .profile as "alias su="su myaccount". My external application logs in with the first account no problem, it then runs 'exec /bin/sh' and then tries to su with the myaccount password but it comes back with 'incorrect password'. If I use an ssh account, login with my first account and then su with myaccount password it works fine. It looks like the 'exec /bin/sh' does not take the alias. /bin/sh points to bash. I have the alias in .bashrc, .profile, .shrc and .bash_profile but none of this works.

any ideas on how to get the alias to work with the /bin/sh shell?

Thanks

Stu
 
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. AIX

Redistribution bin required for AIX. j7r164redist.7.1.0.25.bin

Hi, I am planning to install a version of Informatica on my AIX box. It requires a specific java build in pap6470_27sr2-20141101_01(SR2). The current link for IBM 64-bit SDK for AIX®, JavaTM Technology Edition, Version 7 Release 1 has a more recent version in j7r164redist.7.1.0.75.bin. Is... (4 Replies)
Discussion started by: meetpraveens
4 Replies

2. UNIX for Dummies Questions & Answers

SUDO help with command alias

Hi there, I'm trying to setup sudo privileges for a user, Oracle in this case, to run Unix commands like mv,chmod, chown, mkdir, rmdir against their own set of commands or scripts. Is there an easier way to do this than to give Unix commands for each of their respective commands as shown below... (2 Replies)
Discussion started by: mbak
2 Replies

3. OS X (Apple)

When to use /Users/m/bin instead of /usr/local/bin (& whats the diff?)?

Q1. I understand that /usr/local/bin means I can install/uninstall stuff in here and have any chance of messing up my original system files or effecting any other users. I created this directory myself. But what about the directory I didn't create, namely /Users/m/bin? How is that directory... (1 Reply)
Discussion started by: michellepace
1 Replies

4. Cybersecurity

sudo /bin/sh or sudo su -

we are looking at changing the way we get root on our network. in our current system if an admin needs root access he just gets the root password and uses an su. some of our staff have decided that a sudo to "/bin/sh" will be easer. some of our staff think a sudo to "su -" will be better. I... (0 Replies)
Discussion started by: robsonde
0 Replies

5. UNIX for Dummies Questions & Answers

Alias /usr/bin to /bin in profile

Hi! All the basic linux commands, ie. echo, find, etc, are located in /bin. I have a couple of programs that have these commands pointed towards /usr/bin, ie, /usr/bin/echo (even though the actual 'echo' command is in /bin). How can I alias or redirect or link the /usr/bin to /bin just for this... (6 Replies)
Discussion started by: dancerat
6 Replies

6. UNIX for Dummies Questions & Answers

fuser: difference with bin/sh and bin/ksh shell script

Hi, I have a problem I don't understand with fuser. I launch a simple shell script mysleep.sh: I launch the command fuser -fu mysleep.sh but fuser doesn't return anything excepted: mysleep: Then I modify my script switching from #!/bin/sh to #!/bin/ksh I launch the command fuser -fu... (4 Replies)
Discussion started by: Peuj
4 Replies

7. Shell Programming and Scripting

'exec /bin/sh' breaks alias

I have an application that requires su to root in order to run some commands. Unfortunately, my corporate policy only allows sudo so I created an alias in .profile as "alias su="su myaccount". My external application logs in with the first account no problem, it then runs 'exec /bin/sh' and then... (1 Reply)
Discussion started by: stulincoln
1 Replies

8. Shell Programming and Scripting

sudo problems

I am trying to execute a command via sudo through ssh... something like this... ssh -t a@b "sudo command" getting an error saying sudo: command not found what could be the prb? (3 Replies)
Discussion started by: wannalearn
3 Replies

9. UNIX for Advanced & Expert Users

alias and sudo

I'm using personal user to enter telnet session then manually connecting to a generic user using the following : sudo -H -u $1 ksh -c ". ~$1/.profile && cd ~$1 && ksh" ; where $1 is the generic user. It works but in the ".profile" execution , the alias are not working when the generic... (7 Replies)
Discussion started by: Nicol
7 Replies

10. UNIX for Dummies Questions & Answers

/bin/sh: /usr/bin/vi: No such file or directory when doing crontab

I just set up an ftp server with Red Hat 5.2. I am doing the work, I'm baby stepping, but it seems like every step I get stuck. Currently, I'm trying to set up a crontab job, but I'm getting the following message: /bin/sh: /usr/bin/vi: No such file or directory. I see that vi exists in /bin/vi,... (3 Replies)
Discussion started by: kwalter
3 Replies
Login or Register to Ask a Question

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)