02-16-2019
Quote:
Originally Posted by
paqman
I have a coworker that has set up some funky aliases in /etc/bash.alias, and he insists on leaving them that way.
First off: if they are
his aliases and are not necessary for the working of the system as a whole they have no business being there. They should go to
his profile, rc-script or whatever he uses to configure
his session. I would make that absolutely clear to him in your position.
This is something that always put me off on Linux systems: instead of putting what is absolutely necessary into the
systems configuration and letting everybody take it from there Linux distributions have usually some guy force what he thinks is fine onto the whole world.
Quote:
Originally Posted by
paqman
Anyway, I was wondering if there were a way for me to sudo to root without reading /etc/bash.alias, or maybe have it re-source my personal .bashrc file after I sudo to root?
Using sudo you can find out "where you came from", that is: which user you used to switch into that UID. This way you could set up some mechanism which one (out of several) configurations to apply, as RudiC already hinted at. (Again: only, if
his configuration is not mixed up with the
systems configuration, so no putting what belongs to
/home/<someuser>/.bashrc into
/etc/bashrc (or similarily general configuration scripts.)
Second: you can use the "SETENV:" and "NOSETENV:" directives in
/etc/sudoers and their respective commandline equivalents ("-E", etc.) for
sudo.
I hope this helps.
bakunin
These 3 Users Gave Thanks to bakunin For This Post:
10 More Discussions You Might Find Interesting
1. Linux
Hi all..
I'm secering a RH 2.1 server, with gnome (not my choice...), as X manager.
Is ther anyway to get sudo ask for root password other then the actual user's password? Like when you launch the graphical IHM to create a new user, it asks for root's password? Is there a way to do the same... (5 Replies)
Discussion started by: penguin-friend
5 Replies
2. AIX
Guy's
I'm trying to add some lines in sudo by useing this command visudo
# 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
# %wheel ALL=(ALL) NOPASSWD: ALL
#... (5 Replies)
Discussion started by: ITHelper
5 Replies
3. UNIX for Dummies Questions & Answers
I'm actually working with a Ubuntu-System here and have a question about executing a command with 'sudo'.
I tried and got a error message like "not allowed".
After this I logged in with 'sudo -s' and typed the command without 'sudo'. This worked well.
Can please somebody explain me this... (0 Replies)
Discussion started by: daWonderer
0 Replies
4. UNIX for Dummies Questions & Answers
I've been through many threads before i decide to create a separate thread.
I can't really find the solution to my (simple) problem.
Here's what I'm trying to achieve:
As "canar" user I want to run a command, let's say "/opt/ocaml/bin/ocaml" as "duck" user.
The only to achieve this is to... (1 Reply)
Discussion started by: canar
1 Replies
5. UNIX for Dummies Questions & Answers
Anyone able to explain why if i run "sudo -i" or "sudo -s" i am able to get into root by just keying my own password?
How to avoid this from happening coz i need all the users to use su - only. (2 Replies)
Discussion started by: timmywong
2 Replies
6. UNIX for Dummies Questions & Answers
Hi All,
I need to give an user sudo ability to root.
We have also generated RSA key but unable to proceed further.
For example after a user logs into the server normally and when he executes below command
$ssh root@server_name
This should take you to root prompt #
Please help me.... (3 Replies)
Discussion started by: Rockyc3400
3 Replies
7. Cybersecurity
My friend has found a bug with sudo.
His organization has Linux laptops with no root access to users. Policy pushing is through Puppet.
But doing sudo sudo twice he is able to access root.
Do you guys have any clue, how's that possible, usually sudo su is restricted. (8 Replies)
Discussion started by: nixhead
8 Replies
8. Red Hat
I have a set of RHEL 5 boxes running our ERP software on Oracle databases. I need to allow my DBA's to su to oracle and one other account (banner) without knowing the oracle or banner password. But I need to prevent them from su'ing to any other user especially root. I only want them to be able to... (1 Reply)
Discussion started by: westmoreland
1 Replies
9. UNIX for Beginners Questions & Answers
i have tried to use a sudo command from a user level . but instead of asking for user password it asked for root password . how should i go about it .
james@opensuse:/etc> sudo ifconfig
root's password:
And i wish to ask how should i allow a list of command to be allowed to used for a... (4 Replies)
Discussion started by: lobsang
4 Replies
10. Solaris
Hello,
It is Solaris-10. There is a file as /opt/vpp/dom1.2/pdd/today_23. It is always generated by root, so owned by root only.
This file has to be deleted as part of application restart always and that is done by app_user and SA is always involved to do rm on that file.
Is it possible to give... (9 Replies)
Discussion started by: solaris_1977
9 Replies
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)