06-16-2002
I use an AIX 4.3.3 box. root can only log in from the terminal.
The only way to get to root remotely is to log in using my id and su root. No other person can su root or log in to root remotely. With AIX there is an su log file that lists all attempt to su another id. When root logs in my ID is sent mail indicating the time and port of the login. Therefore I know if root is compromised. I then can search the su log files to see who attempted or sucessfully cracked my root password.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Ok heres the situation
I've been studying Solaris 8 for about 6 months now and some things click in my head but others don't.
One of the things that don't click are file permissions.
For example I login at work and I use the ls -l command to get a long listing of the files w/ the permissions.... (2 Replies)
Discussion started by: eloquent99
2 Replies
2. UNIX for Dummies Questions & Answers
Is it possible to set owner to a group? I need to have a group own a process, because there will be 3 diffrent persons that will start and stop this process. They can not use the same users cause och back logging. we need to know who end when a certian user start/stops processes. (1 Reply)
Discussion started by: dozy
1 Replies
3. UNIX for Dummies Questions & Answers
What does the following permission indicate?
-rwSr----- 1 oracle dba 1536 Nov 7 17:05 orapwRTMDB
Thanks,
Rahul. (1 Reply)
Discussion started by: rahulrathod
1 Replies
4. UNIX for Dummies Questions & Answers
Hi,
When I listed one directory in Sun, it showed that :
-rwsr-xr-x 1 root bsmbin 78004 Oct 21 2004 bsmprsm
I don't know meaning of the character "s" in "rws" above. I have searched in Sun admin documents but no result. Would you please explain it ? :)
Thank you so much. (1 Reply)
Discussion started by: msg098
1 Replies
5. UNIX for Dummies Questions & Answers
Hi all,
I created testuser. by following command.
/usr/sbin/adduser -n test -d /disk05/collections/GET/testdata/
and then set its password by following command.
passwd testuser
When I login to system by testuser, it enters everything is ok.
The problem is how to set permission to this... (3 Replies)
Discussion started by: mr_bold
3 Replies
6. Ubuntu
Pictures by worthamtx - Photobucket
The URL is graphic view my present concern. Old partition working great sdb1
both appear on nautilus, both deliver icons to desk top. Based on the label handling of gparted results I tried following with success
sudo mkdir /media/disk/data
sudo chown... (1 Reply)
Discussion started by: 77yrold
1 Replies
7. UNIX for Dummies Questions & Answers
Hello
Whenever we want to oen any type of file by name, we must have execute perm. in each
dir. mentioned in the name. I changed the dir permission using chmod to test the validity of this statement.
but i still can open the file
-------
any guides would be appreciable (2 Replies)
Discussion started by: dr_mabuse
2 Replies
8. UNIX for Dummies Questions & Answers
I dont understand why permission changes are being such a pain in the bum even after I manually changed them through properties....Anyone know what to do here because even thoguh in properties the permissions make me local admin over in the Cygwin its not working..
... (5 Replies)
Discussion started by: okhawaja
5 Replies
9. Linux
I am using korn shell
When I type in Telnet on cmd line, I get message
"cannot execute"
How can I get permission to execute command ? In which dir is telnet located ? I looked in /usr/bin dir. but its not there
Thanks (1 Reply)
Discussion started by: paramshamnani
1 Replies
10. Ubuntu
Trying to get date into the txt file.
It says
Permission denied.
echo $(date +%I:%M:%S_%D) >> /tmp/systemd_suspend_test_err.txt
exec 2>> /tmp/systemd_suspend_test_err.txt
if ; then
# Do the thing you want before suspend here
echo "we are suspending $(date +%I:%M:%S_%D)."
elif ;... (5 Replies)
Discussion started by: drew77
5 Replies
LEARN ABOUT LINUX
sudo_root
sudo_root(8) System Manager's Manual sudo_root(8)
NAME
sudo_root - How to run administrative commands
SYNOPSIS
sudo command
sudo -i
INTRODUCTION
By default, the password for the user "root" (the system administrator) is locked. This means you cannot login as root or use su. Instead,
the installer will set up sudo to allow the user that is created during install to run all administrative commands.
This means that in the terminal you can use sudo for commands that require root privileges. All programs in the menu will use a graphical
sudo to prompt for a password. When sudo asks for a password, it needs your password, this means that a root password is not needed.
To run a command which requires root privileges in a terminal, simply prepend sudo in front of it. To get an interactive root shell, use
sudo -i.
ALLOWING OTHER USERS TO RUN SUDO
By default, only the user who installed the system is permitted to run sudo. To add more administrators, i. e. users who can run sudo, you
have to add these users to the group 'admin' by doing one of the following steps:
* In a shell, do
sudo adduser username admin
* Use the graphical "Users & Groups" program in the "System settings" menu to add the new user to the admin group.
BENEFITS OF USING SUDO
The benefits of leaving root disabled by default include the following:
* Users do not have to remember an extra password, which they are likely to forget.
* The installer is able to ask fewer questions.
* It avoids the "I can do anything" interactive login by default - you will be prompted for a password before major changes can happen,
which should make you think about the consequences of what you are doing.
* Sudo adds a log entry of the command(s) run (in /var/log/auth.log).
* Every attacker trying to brute-force their way into your box will know it has an account named root and will try that first. What they do
not know is what the usernames of your other users are.
* Allows easy transfer for admin rights, in a short term or long term period, by adding and removing users from the admin group, while not
compromising the root account.
* sudo can be set up with a much more fine-grained security policy.
* On systems with more than one administrator using sudo avoids sharing a password amongst them.
DOWNSIDES OF USING SUDO
Although for desktops the benefits of using sudo are great, there are possible issues which need to be noted:
* Redirecting the output of commands run with sudo can be confusing at first. For instance consider
sudo ls > /root/somefile
will not work since it is the shell that tries to write to that file. You can use
ls | sudo tee /root/somefile
to get the behaviour you want.
* In a lot of office environments the ONLY local user on a system is root. All other users are imported using NSS techniques such as
nss-ldap. To setup a workstation, or fix it, in the case of a network failure where nss-ldap is broken, root is required. This tends to
leave the system unusable. An extra local user, or an enabled root password is needed here.
GOING BACK TO A TRADITIONAL ROOT ACCOUNT
This is not recommended!
To enable the root account (i.e. set a password) use:
sudo passwd root
Afterwards, edit the sudo configuration with sudo visudo and comment out the line
%admin ALL=(ALL) ALL
to disable sudo access to members of the admin group.
SEE ALSO
sudo(8), https://wiki.ubuntu.com/RootSudo
February 8, 2006 sudo_root(8)