05-31-2011
These accounts are part of the operating system. They aren't used by real users.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I am writting a daemon in python which should start at system start up with all inet.d services
on an NIS server. Then it should listen to any user login and then start a new process for that user on his login which will continue throughout his entire session.
Can anyone give any help or any... (1 Reply)
Discussion started by: thinkgeek
1 Replies
2. UNIX for Dummies Questions & Answers
Hello everyone, traditionally a user can log in on more than one machine as much as they want. In AIX 4.3, Is there a way to make it so that if the user is already logged on, the system will not let them log on, therefor not run their logon profile script again? (limit the user to one machine at a... (1 Reply)
Discussion started by: raidzero
1 Replies
3. Solaris
I want to apply patches in multiuser mode but stop logins of other users while I do it?
What is the best way to do this?
I will be connected to the system via a putty session over a serial cable from another system (console is messed up)...
Should I put in a dummy passwd and shadow file... (7 Replies)
Discussion started by: NewSolarisAdmin
7 Replies
4. AIX
I want to know how I can turn off and turn on login logging. We have a server that appears to have stopped logging user logins. Running the who command shows nothing and the last command shows no logins for a month. The var/adm/wtmp file isn't full and there is plenty of space in the var file... (2 Replies)
Discussion started by: daveisme
2 Replies
5. Shell Programming and Scripting
Hello, I want to write a script that takes a username as input and outputs the user's logins sorted by duration. Also I want to exclude the "still logged in" entries.
I use the "last" command but Im having problems sorting the entries based on the duration.
Can you help me?
Thanks a lot =) (4 Replies)
Discussion started by: ddante
4 Replies
6. Homework & Coursework Questions
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
List the last 3 times you logged into the hottub and the command(s) you used to obtain this information
2.... (12 Replies)
Discussion started by: iw2198
12 Replies
7. Solaris
Is it possible to configure a Solaris server to authenticate users against an Active Directory server when logging in via ssh?
I've seen some docs out there, I've followed their instructions, but it does not work. And I'm beginning to wonder if it is possible or even supported by Oracle. The... (2 Replies)
Discussion started by: BG_JrAdmin
2 Replies
8. Red Hat
Hi team,
I tried to modify the /etc/security/limits.conf file to limit the root user for more one login. I added the line in limits.conf file like:
@root hard maxlogins 1
I also tried to modify /etc/ssh/sshd_config to limit the root userlogin by adding this:
... (10 Replies)
Discussion started by: leo_ultra_leo
10 Replies
9. Solaris
Ok got a strange one here. None of my user accounts are able to login into the system. When trying to ssh to the server i get the following.
Could not chdir to home directory /home/<homedir>: Permission denied
/bin/sh: Permission denied
I checked the permissions on the home directory and even... (7 Replies)
Discussion started by: JoeDirte
7 Replies
10. UNIX for Beginners Questions & Answers
Hi folks,
I am fairly a beginner when it comes to Solaris OS administration, but part of my job somehow has scope to provide L1-level of OS administration over a few solaris servers.
Now, we have a requirement to limit the number of simultaneous ssh logins/sessions to the server, sort of... (0 Replies)
Discussion started by: engrcha
0 Replies
LEARN ABOUT PLAN9
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)