Annotated edit history of
safe_finger(8) version 4, including all changes.
View license author blame.
| Rev |
Author |
# |
Line |
| 1 |
perry |
1 |
SAFE_FINGER |
| |
|
2 |
!!!SAFE_FINGER |
| |
|
3 |
NAME |
| |
|
4 |
SYNOPSIS |
| |
|
5 |
DESCRIPTION |
| |
|
6 |
SEE ALSO |
| |
|
7 |
AUTHOR |
| |
|
8 |
---- |
| |
|
9 |
!!NAME |
| |
|
10 |
|
| |
|
11 |
|
| |
|
12 |
safe_finger - finger client wrapper that protects against nasty stuff from finger servers |
| |
|
13 |
!!SYNOPSIS |
| |
|
14 |
|
| |
|
15 |
|
| |
|
16 |
__safe_finger [[finger_options]__ |
| |
|
17 |
!!DESCRIPTION |
| |
|
18 |
|
| |
|
19 |
|
| |
|
20 |
The __safe_finger__ command protects against nasty stuff |
| |
|
21 |
from finger servers. Use this program for automatic reverse |
| |
|
22 |
finger probes from the __tcp_wrapper (tcpd)__ , not the |
| |
|
23 |
raw finger command. The __safe_finger__ command makes |
| |
|
24 |
sure that the finger client is not run with root privileges. |
| |
|
25 |
It also runs the finger client with a defined PATH |
| |
|
26 |
environment. __safe_finger__ will also protect you from |
| |
|
27 |
problems caused by the output of some finger servers. The |
| |
|
28 |
problem: some programs may react to stuff in the first |
| |
|
29 |
column. Other programs may get upset by thrash anywhere on a |
| |
|
30 |
line. File systems may fill up as the finger server keeps |
| |
|
31 |
sending data. Text editors may bomb out on extremely long |
| |
|
32 |
lines. The finger server may take forever because it is |
| |
|
33 |
somehow wedged. __safe_finger__ takes care of all this |
| |
|
34 |
badness. |
| |
|
35 |
!!SEE ALSO |
| |
|
36 |
|
| |
|
37 |
|
| 4 |
perry |
38 |
hosts_access(5), __hosts_options__(5), |
| 1 |
perry |
39 |
tcpd(8) |
| |
|
40 |
!!AUTHOR |
| |
|
41 |
|
| |
|
42 |
|
| |
|
43 |
Wietse Venema, Eindhoven University of Technology, The |
| |
|
44 |
Netherlands. |
| |
|
45 |
---- |
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.
