Line | |
---|
1 | .TH RHOSTS 5
|
---|
2 | .SH NAME
|
---|
3 | rhosts, hosts.equiv \- trusted remote users or hosts
|
---|
4 | .SH SYNOPSIS
|
---|
5 | .BI ~ user /.rhosts
|
---|
6 | .br
|
---|
7 | .B /etc/hosts.equiv
|
---|
8 | .SH DESCRIPTION
|
---|
9 | The per user
|
---|
10 | .B .rhosts
|
---|
11 | and the per system
|
---|
12 | .B hosts.equiv
|
---|
13 | files can be used to allow users to use
|
---|
14 | .B rlogin
|
---|
15 | or
|
---|
16 | .B rsh
|
---|
17 | without a password. The remote login services first check the system wide
|
---|
18 | .B /etc/hosts.equiv
|
---|
19 | file and then the
|
---|
20 | .BI ~ user /.rhosts
|
---|
21 | of the intended user. Both files contain lines of one of two forms:
|
---|
22 | .PP
|
---|
23 | .RS
|
---|
24 | .I host
|
---|
25 | .br
|
---|
26 | .I host ruser
|
---|
27 | .RE
|
---|
28 | .PP
|
---|
29 | The first form tells that any user from
|
---|
30 | .I host
|
---|
31 | is allowed to login to this system under the same name. The second form
|
---|
32 | allows
|
---|
33 | .I ruser
|
---|
34 | from
|
---|
35 | .I host
|
---|
36 | to login.
|
---|
37 | .PP
|
---|
38 | Under MINIX 3
|
---|
39 | .I host
|
---|
40 | may be a pattern using
|
---|
41 | .B "*"
|
---|
42 | as a wildcard. One can use this, carefully one may hope, to allow an
|
---|
43 | entire domain to log in.
|
---|
44 | .I Host
|
---|
45 | may also be an IP address, or a network specification in CIDR form, e.g.
|
---|
46 | 172.16.102.64/27.
|
---|
47 | .SH "SEE ALSO"
|
---|
48 | .BR rlogin (1),
|
---|
49 | .BR rsh (1).
|
---|
50 | .SH NOTES
|
---|
51 | MINIX 3 has no restrictions on becoming super-user remotely. Other systems
|
---|
52 | usually require one to log in as a user and then use
|
---|
53 | .BR su
|
---|
54 | to become root.
|
---|
55 | .PP
|
---|
56 | You must use fully qualified hostnames, it is not possible to
|
---|
57 | omit the domain part.
|
---|
58 | .SH AUTHOR
|
---|
59 | Kees J. Bot <kjb@cs.vu.nl>
|
---|
Note:
See
TracBrowser
for help on using the repository browser.