summaryrefslogtreecommitdiffstats
path: root/share
diff options
context:
space:
mode:
authorbrueffer <brueffer@FreeBSD.org>2003-07-08 21:10:32 +0000
committerbrueffer <brueffer@FreeBSD.org>2003-07-08 21:10:32 +0000
commita2d305114410b3b2ee7b586bff9cc4568ae727d1 (patch)
tree5fadf972ae78aaa23a77cf2c799589e086f5de32 /share
parent3d2e5159d92fde431ac53c9ee408a2103d5b17ee (diff)
downloadFreeBSD-src-a2d305114410b3b2ee7b586bff9cc4568ae727d1.zip
FreeBSD-src-a2d305114410b3b2ee7b586bff9cc4568ae727d1.tar.gz
Grammar fix
PR: 54225 Submitted by: Christopher Nehren <apeiron@comcast.net> MFC after: 3 days
Diffstat (limited to 'share')
-rw-r--r--share/man/man7/security.72
1 files changed, 1 insertions, 1 deletions
diff --git a/share/man/man7/security.7 b/share/man/man7/security.7
index 4378522..af813e7 100644
--- a/share/man/man7/security.7
+++ b/share/man/man7/security.7
@@ -631,7 +631,7 @@ Ssh works quite well in every respect except when it is set up to
forward encryption keys.
What this means is that if you have a secure workstation holding
keys that give you access to the rest of the system, and you ssh to an
-unsecure machine, your keys becomes exposed. The actual keys themselves are
+unsecure machine, your keys become exposed. The actual keys themselves are
not exposed, but ssh installs a forwarding port for the duration of your
login and if a hacker has broken root on the unsecure machine he can utilize
that port to use your keys to gain access to any other machine that your
OpenPOWER on IntegriCloud