summaryrefslogtreecommitdiff
path: root/ssh-keyscan.0
diff options
context:
space:
mode:
authorColin Watson <cjwatson@debian.org>2005-01-04 13:07:27 +0000
committerColin Watson <cjwatson@debian.org>2005-01-04 13:07:27 +0000
commitfd0f611b70a83d80fe8793af785542ee5541b7cd (patch)
treebededd22bb7eeec52e20083237ab7e4113445a16 /ssh-keyscan.0
parentc44fe9a5b9d3db96a7249b04d915f17e4a3a3b04 (diff)
parentebd2ce335af5861020c79fddb1ae35c03bf036cf (diff)
Merge 3.9p1 to the trunk.
Diffstat (limited to 'ssh-keyscan.0')
-rw-r--r--ssh-keyscan.010
1 files changed, 5 insertions, 5 deletions
diff --git a/ssh-keyscan.0 b/ssh-keyscan.0
index c1334378f..a218fbf2b 100644
--- a/ssh-keyscan.0
+++ b/ssh-keyscan.0
@@ -53,10 +53,10 @@ DESCRIPTION
53 53
54SECURITY 54SECURITY
55 If a ssh_known_hosts file is constructed using ssh-keyscan without veri- 55 If a ssh_known_hosts file is constructed using ssh-keyscan without veri-
56 fying the keys, users will be vulnerable to attacks. On the other hand, 56 fying the keys, users will be vulnerable to man in the middle attacks.
57 if the security model allows such a risk, ssh-keyscan can help in the de- 57 On the other hand, if the security model allows such a risk, ssh-keyscan
58 tection of tampered keyfiles or man in the middle attacks which have be- 58 can help in the detection of tampered keyfiles or man in the middle at-
59 gun after the ssh_known_hosts file was created. 59 tacks which have begun after the ssh_known_hosts file was created.
60 60
61FILES 61FILES
62 Input format: 62 Input format:
@@ -100,4 +100,4 @@ BUGS
100 This is because it opens a connection to the ssh port, reads the public 100 This is because it opens a connection to the ssh port, reads the public
101 key, and drops the connection as soon as it gets the key. 101 key, and drops the connection as soon as it gets the key.
102 102
103OpenBSD 3.5 January 1, 1996 2 103OpenBSD 3.6 January 1, 1996 2