01-28-2009
Well to help you, we need to uderstand..
What do you call 5 root users?
5 sepaprate accounts with uid 0?
5 users that know roots passwd?
5 users that can su root?
the 1rst case should not be a problem since each has its history file
the 2 other case, quite easy unless the user just does su ( no - sign) in which case he will not read roots profile..., it depends on how the users connect themselves...
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi!! Experts,
I have a typical scenario here in which several users have access to a particular login .. say "build".
None of the users know the passwd for this login.
The name of some of the user have been to .rhosts file.
The users can connect only by doing a rlogin to this id and then... (4 Replies)
Discussion started by: jyotipg
4 Replies
2. SCO
UnixWare 7, Release 7.1.3
We have a customer that has frequent issues with Non-Root users being unable to print. They are able to print w/o issues, but all of the sudden it stops working. The only workaround we have at this point is to reboot the server. It is happening weekly according to... (1 Reply)
Discussion started by: cfshd
1 Replies
3. Solaris
We have a Solaris box. I noticed that whenever any non-root user logins into the box and issues the command id the output is (for example) uid=42568(sam) gid=1245(sam) euid=0(root) egid=2(bin). I have not given any privileges to anyone explicitly. When I issued ls -l in the /usr/bin directory I... (1 Reply)
Discussion started by: chrisanto_2000
1 Replies
4. Solaris
hello,
I have a challenge to find a way to lock down a file in a user's home directory, such that a user can NOT modify, rename, move, delete, etc. The solution needs to be deployable without, for example, having to switch from unix to windows, etc
We are using NFS. We want to lock the... (1 Reply)
Discussion started by: jvmagic
1 Replies
5. UNIX Desktop Questions & Answers
Hi there,
I'm working with a Linux server and now I can get a daily Logwatch mail ... my question is:since there are too many users with root password (...in my opinion... :mad:) how could I prevent to delete information about "su" log?
Thanks in advance,
GB (3 Replies)
Discussion started by: Giordano Bruno
3 Replies
6. AIX
Hi All
How can track what commands are entered by the Root user. Is there a log besides using the history command that lists all commands entered for a period of time.
thanks:o (6 Replies)
Discussion started by: pashan
6 Replies
7. Solaris
I'm using Solaris 10. I want to restrict users from executing this dangerous command.
rm -rf *
But they should be able to perform the below actions:
rm -rf *.*
rm -rf filename
rm -rf directory
Is it possible? If yes then pls let me know how to do it? (7 Replies)
Discussion started by: Arun_Linux
7 Replies
8. UNIX for Dummies Questions & Answers
Hi all,
I have a small problem. When I log in as root and try to switch to any other user using su -user, then it is giving an error saying libncurses.so permission denied. Can you help me?
Thank you in advance.
Sai. (1 Reply)
Discussion started by: sai2krishna
1 Replies
9. Shell Programming and Scripting
I need to list users in /etc/passwd with root's GID or UID or /root as home directory
If we have these entries in /etc/passwd
root:x:0:0:root:/root:/bin/bash
rootgooduser1:x:100:100::/home/gooduser1:/bin/bash
baduser1:x:0:300::/home/baduser1:/bin/bash... (6 Replies)
Discussion started by: anil510
6 Replies
10. Shell Programming and Scripting
Hi folks,
I have the basic query that there are 3 unix boxes having their individual access now in my team there are 4 members who are using the same credentials to access those 3 boxes through putty ssh from their windows desktop , now if i want to check which 4 members have executed the... (1 Reply)
Discussion started by: punpun66
1 Replies
LEARN ABOUT X11R4
hosts.equiv
HOSTS.EQUIV(5) Linux Programmer's Manual HOSTS.EQUIV(5)
NAME
hosts.equiv - list of hosts and users that are granted "trusted" r command access to your system
DESCRIPTION
The file /etc/hosts.equiv allows or denies hosts and users to use the r-commands (e.g., rlogin, rsh, or rcp) without supplying a password.
The file uses the following format:
+|[-]hostname|+@netgroup|-@netgroup [+|[-]username|+@netgroup|-@netgroup]
The hostname is the name of a host which is logically equivalent to the local host. Users logged into that host are allowed to access
like-named user accounts on the local host without supplying a password. The hostname may be (optionally) preceded by a plus (+) sign. If
the plus sign is used alone, it allows any host to access your system. You can explicitly deny access to a host by preceding the hostname
by a minus (-) sign. Users from that host must always supply additional credentials, including possibly a password. For security reasons
you should always use the FQDN of the hostname and not the short hostname.
The username entry grants a specific user access to all user accounts (except root) without supplying a password. That means the user is
NOT restricted to like-named accounts. The username may be (optionally) preceded by a plus (+) sign. You can also explicitly deny access
to a specific user by preceding the username with a minus (-) sign. This says that the user is not trusted no matter what other entries
for that host exist.
Netgroups can be specified by preceding the netgroup by an @ sign.
Be extremely careful when using the plus (+) sign. A simple typographical error could result in a standalone plus sign. A standalone plus
sign is a wildcard character that means "any host"!
FILES
/etc/hosts.equiv
NOTES
Some systems will honor the contents of this file only when it has owner root and no write permission for anybody else. Some exceptionally
paranoid systems even require that there be no other hard links to the file.
Modern systems use the Pluggable Authentication Modules library (PAM). With PAM a standalone plus sign is considered a wildcard character
which means "any host" only when the word promiscuous is added to the auth component line in your PAM file for the particular service
(e.g., rlogin).
EXAMPLE
Below are some example /etc/host.equiv or ~/.rhosts files.
Allow any user to log in from any host:
+
Allow any user from host with a matching local account to log in:
host
Note: the use of +host is never a valid syntax, including attempting to specify that any user from the host is allowed.
Allow any user from host to log in:
host +
Note: this is distinct from the previous example since it does not require a matching local account.
Allow user from host to log in as any non-root user:
host user
Allow all users with matching local accounts from host to log in except for baduser:
host -baduser
host
Deny all users from host:
-host
Note: the use of -host -user is never a valid syntax, including attempting to specify that a particular user from the host is not trusted.
Allow all users with matching local accounts on all hosts in a netgroup:
+@netgroup
Disallow all users on all hosts in a netgroup:
-@netgroup
Allow all users in a netgroup to log in from host as any non-root user:
host +@netgroup
Allow all users with matching local accounts on all hosts in a netgroup except baduser:
+@netgroup -baduser
+@netgroup
Note: the deny statements must always precede the allow statements because the file is processed sequentially until the first matching rule
is found.
SEE ALSO
rhosts(5), rlogind(8), rshd(8)
COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the
latest version of this page, can be found at https://www.kernel.org/doc/man-pages/.
Linux 2015-07-23 HOSTS.EQUIV(5)