summaryrefslogtreecommitdiff
path: root/ssh-keyscan.1
diff options
context:
space:
mode:
authorDarren Tucker <dtucker@zip.com.au>2004-07-17 16:13:15 +1000
committerDarren Tucker <dtucker@zip.com.au>2004-07-17 16:13:15 +1000
commit3ca45082017f0fcaf01b0bf781ae33cf1cc57e27 (patch)
tree8d304e08c3a71e956d6c532a469c840592659c4e /ssh-keyscan.1
parentfc9597034b819b295966f61d8dc797b53fda45c7 (diff)
- brad@cvs.openbsd.org 2004/07/12 23:34:25
[ssh-keyscan.1] Fix incorrect macro, .I -> .Em From: Eric S. Raymond <esr at thyrsus dot com> ok jmc@
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 572751f6..9efcf521 100644
--- a/ssh-keyscan.1
+++ b/ssh-keyscan.1
@@ -1,4 +1,4 @@
-.\" $OpenBSD: ssh-keyscan.1,v 1.17 2003/06/10 09:12:11 jmc Exp $
+.\" $OpenBSD: ssh-keyscan.1,v 1.18 2004/07/12 23:34:25 brad Exp $
.\"
.\" Copyright 1995, 1996 by David Mazieres <dm@lcs.mit.edu>.
.\"
@@ -97,7 +97,7 @@ to use IPv6 addresses only.
If a ssh_known_hosts file is constructed using
.Nm
without verifying the keys, users will be vulnerable to
-.I man in the middle
+.Em man in the middle
attacks.
On the other hand, if the security model allows such a risk,
.Nm