summaryrefslogtreecommitdiff
path: root/ssh-keyscan.1
diff options
context:
space:
mode:
authorBen Lindstrom <mouring@eviladmin.org>2001-04-19 20:31:02 +0000
committerBen Lindstrom <mouring@eviladmin.org>2001-04-19 20:31:02 +0000
commitf73e05eca801c3a3488caa3b6bf1585ab7e2c13a (patch)
treeb5f1450bd99eb0da15d42956dccf249691d25440 /ssh-keyscan.1
parentbc70992058852307479e08e98e286e9aa3566493 (diff)
- ian@cvs.openbsd.org 2001/04/18 16:21:05
[ssh-keyscan.1] Fix typo reported in PR/1779
Diffstat (limited to 'ssh-keyscan.1')
-rw-r--r--ssh-keyscan.14
1 files changed, 2 insertions, 2 deletions
diff --git a/ssh-keyscan.1 b/ssh-keyscan.1
index eace55dd..4db8c5f1 100644
--- a/ssh-keyscan.1
+++ b/ssh-keyscan.1
@@ -1,4 +1,4 @@
-.\" $OpenBSD: ssh-keyscan.1,v 1.4 2001/03/01 03:38:33 deraadt Exp $
+.\" $OpenBSD: ssh-keyscan.1,v 1.5 2001/04/18 16:21:05 ian Exp $
.\"
.\" Copyright 1995, 1996 by David Mazieres <dm@lcs.mit.edu>.
.\"
@@ -33,7 +33,7 @@ uses non-blocking socket I/O to contact as many hosts as possible in
parallel, so it is very efficient. The keys from a domain of 1,000
hosts can be collected in tens of seconds, even when some of those
hosts are down or do not run ssh. You do not need login access to the
-machines you are scanning, nor does does the scanning process involve
+machines you are scanning, nor does the scanning process involve
any encryption.
.Sh SECURITY
If you make an ssh_known_hosts file using