summaryrefslogtreecommitdiff
path: root/ssh-keyscan.1
diff options
context:
space:
mode:
authorBen Lindstrom <mouring@eviladmin.org>2001-09-12 18:35:30 +0000
committerBen Lindstrom <mouring@eviladmin.org>2001-09-12 18:35:30 +0000
commit594e20389490bf91724dc903cb9aaa92d037b7a4 (patch)
tree8bcf855dccd896ee87ae815aeeb80f87d6035e08 /ssh-keyscan.1
parentedc0cf26d11d708320ade92e066d4f3e84e20112 (diff)
- deraadt@cvs.openbsd.org 2001/09/05 06:23:07
[scp.1 sftp.1 ssh.1 ssh-agent.1 sshd.8 ssh-keygen.1 ssh-keyscan.1] avoid first person in manual pages
Diffstat (limited to 'ssh-keyscan.1')
-rw-r--r--ssh-keyscan.118
1 files changed, 9 insertions, 9 deletions
diff --git a/ssh-keyscan.1 b/ssh-keyscan.1
index 1a358b338..17f73406e 100644
--- a/ssh-keyscan.1
+++ b/ssh-keyscan.1
@@ -1,4 +1,4 @@
1.\" $OpenBSD: ssh-keyscan.1,v 1.11 2001/08/23 18:08:59 stevesk Exp $ 1.\" $OpenBSD: ssh-keyscan.1,v 1.12 2001/09/05 06:23:07 deraadt Exp $
2.\" 2.\"
3.\" Copyright 1995, 1996 by David Mazieres <dm@lcs.mit.edu>. 3.\" Copyright 1995, 1996 by David Mazieres <dm@lcs.mit.edu>.
4.\" 4.\"
@@ -35,9 +35,9 @@ scripts.
35uses non-blocking socket I/O to contact as many hosts as possible in 35uses non-blocking socket I/O to contact as many hosts as possible in
36parallel, so it is very efficient. The keys from a domain of 1,000 36parallel, so it is very efficient. The keys from a domain of 1,000
37hosts can be collected in tens of seconds, even when some of those 37hosts can be collected in tens of seconds, even when some of those
38hosts are down or do not run ssh. You do not need login access to the 38hosts are down or do not run ssh. For scanning, one does not need
39machines you are scanning, nor does the scanning process involve 39login access to the machines that are being scanned, nor does the
40any encryption. 40scanning process involve any encryption.
41.Pp 41.Pp
42The options are as follows: 42The options are as follows:
43.Bl -tag -width Ds 43.Bl -tag -width Ds
@@ -88,15 +88,15 @@ Forces
88to use IPv6 addresses only. 88to use IPv6 addresses only.
89.El 89.El
90.Sh SECURITY 90.Sh SECURITY
91If you make an ssh_known_hosts file using 91If a ssh_known_hosts file is constructed using
92.Nm 92.Nm
93without verifying the keys, you will be vulnerable to 93without verifying the keys, users will be vulnerable to
94.I man in the middle 94.I man in the middle
95attacks. 95attacks.
96On the other hand, if your security model allows such a risk, 96On the other hand, if the security model allows such a risk,
97.Nm 97.Nm
98can help you detect tampered keyfiles or man in the middle attacks which 98can help in the detection of tampered keyfiles or man in the middle
99have begun after you created your ssh_known_hosts file. 99attacks which have begun after the ssh_known_hosts file was created.
100.Sh EXAMPLES 100.Sh EXAMPLES
101.Pp 101.Pp
102Print the 102Print the