diff --git a/en_US.ISO8859-1/books/handbook/security/chapter.sgml b/en_US.ISO8859-1/books/handbook/security/chapter.sgml
index 28ab8b0395..a5d208f2b3 100644
--- a/en_US.ISO8859-1/books/handbook/security/chapter.sgml
+++ b/en_US.ISO8859-1/books/handbook/security/chapter.sgml
@@ -3805,18 +3805,18 @@ ipfw add 1 allow ipencap from W.X.Y.Z to A.B.C.D
OpenSSH
- Secure shell is a set of network connectivity tools used to
+ OpenSSH is a set of network connectivity tools used to
access remote machines securely. It can be used as a direct
replacement for rlogin,
rsh, rcp, and
telnet. Additionally, any other TCP/IP
- connections can be tunneled/forwarded securely through ssh.
- ssh encrypts all traffic to effectively eliminate eavesdropping,
+ connections can be tunneled/forwarded securely through SSH.
+ OpenSSH encrypts all traffic to effectively eliminate eavesdropping,
connection hijacking, and other network-level attacks.
- OpenSSH is maintained by the OpenBSD project, and is based
+ OpenSSH is maintained by the OpenBSD project, and is based
upon SSH v1.2.12 with all the recent bug fixes and updates. It
- is compatible with both SSH protocols 1 and 2. OpenSSH has been
+ is compatible with both SSH protocols 1 and 2. OpenSSH has been
in the base system since FreeBSD 4.0.
@@ -3826,7 +3826,7 @@ ipfw add 1 allow ipencap from W.X.Y.Z to A.B.C.D
data is sent over the network in an clear, un-encrypted form.
Network sniffers anywhere in between the client and server can
steal your user/password information or data transferred in
- your session. OpenSSH offers a variety of authentication and
+ your session. OpenSSH offers a variety of authentication and
encryption methods to prevent this from happening.
@@ -3840,7 +3840,7 @@ ipfw add 1 allow ipencap from W.X.Y.Z to A.B.C.D
Be sure to make the following addition to your
rc.conf file:sshd_enable="YES"
- This will load &man.sshd.8;, the daemon program for ssh,
+ This will load &man.sshd.8;, the daemon program for OpenSSH,
the next time your system initializes. Alternatively, you can
simply run directly the sshd daemon by typing sshd on the command line.
@@ -3875,12 +3875,12 @@ user@example.com's password: *******~/.ssh/known_hosts2 for SSH v2
fingerprints.
- By default, OpenSSH servers are configured to accept both
+ By default, OpenSSH servers are configured to accept both
SSH v1 and SSH v2 connections. The client, however, can choose
between the two. Version 2 is known to be more robust and
secure than its predecessor.
- ssh can be forced to use either protocol
+ The &man.ssh.1; command can be forced to use either protocol
by passing it the or argument
for v1 and v2, respectively.
@@ -3922,7 +3922,7 @@ COPYRIGHT 100% |*****************************| 4735
configuration
- The system-wide configuration files for both the OpenSSH
+ The system-wide configuration files for both the OpenSSH
daemon and client reside within the /etc/ssh
directory.
@@ -3988,7 +3988,7 @@ Your identification has been saved in /home/user/.ssh/identity.
utilities used in managing multiple passworded private keys.The various options and files can be different
- according to the OpenSSH version you have on your system, to
+ according to the OpenSSH version you have on your system, to
avoid problems you should consult the &man.ssh-keygen.1;
manual page.
@@ -4000,11 +4000,11 @@ Your identification has been saved in /home/user/.ssh/identity.
tunneling
- OpenSSH has the ability to create a tunnel to encapsulate
+ OpenSSH has the ability to create a tunnel to encapsulate
another protocol in an encrypted session.The following command tells &man.ssh.1; to create a tunnel
- for telnet.
+ for telnet:&prompt.user; ssh -2 -N -f -L 5023:localhost:23 user@foo.example.com
&prompt.user;
@@ -4019,7 +4019,7 @@ Your identification has been saved in /home/user/.ssh/identity.
Forces ssh to use version 2 of
the protocol. (Do not use if you are working with older
- ssh servers)
+ SSH servers)
@@ -4071,8 +4071,8 @@ Your identification has been saved in /home/user/.ssh/identity.
In the example, port 5023 on
localhost is being forwarded to port
23 on localhost
- of the remote machine. Since 23 is telnet,
- this would create a secure telnet session through an SSH tunnel.
+ of the remote machine. Since 23 is telnet,
+ this would create a secure telnet session through an SSH tunnel.This can be used to wrap any number of insecure TCP protocols
such as SMTP, POP3, FTP, etc.
@@ -4122,7 +4122,7 @@ user@ssh-server.example.com's password: ******Bypassing a Draconian Firewall
- Some network administrators impose extremely Draconian
+ Some network administrators impose extremely draconian
firewall rules, filtering not only incoming connections,
but outgoing connections. You may be only given access
to contact remote machines on ports 22 and 80 for SSH