aboutsummaryrefslogtreecommitdiff
path: root/ssh.1
diff options
context:
space:
mode:
authorDag-Erling Smørgrav <des@FreeBSD.org>2011-09-28 08:14:41 +0000
committerDag-Erling Smørgrav <des@FreeBSD.org>2011-09-28 08:14:41 +0000
commit1e26c29b778d4cac65ea2a83f6089e22fe8f8421 (patch)
tree779b14ae51eee4ed5bde82d3600b03a260319632 /ssh.1
parentc00cf9e642bae52ddf629123ecd72ca32d6157d8 (diff)
downloadsrc-1e26c29b778d4cac65ea2a83f6089e22fe8f8421.tar.gz
src-1e26c29b778d4cac65ea2a83f6089e22fe8f8421.zip
Vendor import of OpenSSH 5.9p1vendor/openssh/5.9p1
Notes
Notes: svn path=/vendor-crypto/openssh/dist/; revision=225825 svn path=/vendor-crypto/openssh/5.9p1/; revision=225826; tag=vendor/openssh/5.9p1
Diffstat (limited to 'ssh.1')
-rw-r--r--ssh.115
1 files changed, 10 insertions, 5 deletions
diff --git a/ssh.1 b/ssh.1
index e3a42b5ad7de..9c1ca4b169a0 100644
--- a/ssh.1
+++ b/ssh.1
@@ -33,8 +33,8 @@
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
-.\" $OpenBSD: ssh.1,v 1.316 2010/11/18 15:01:00 jmc Exp $
-.Dd $Mdocdate: November 18 2010 $
+.\" $OpenBSD: ssh.1,v 1.320 2011/08/02 01:22:11 djm Exp $
+.Dd $Mdocdate: August 2 2011 $
.Dt SSH 1
.Os
.Sh NAME
@@ -392,9 +392,11 @@ Valid commands are:
.Dq check
(check that the master process is running),
.Dq forward
-(request forwardings without command execution) and
+(request forwardings without command execution),
.Dq exit
-(request the master to exit).
+(request the master to exit), and
+.Dq stop
+(request the master to stop accepting further multiplexing requests).
.It Fl o Ar option
Can be used to give options in the format used in the configuration file.
This is useful for specifying options for which there is no separate
@@ -454,6 +456,7 @@ For full details of the options listed below, and their possible values, see
.It PubkeyAuthentication
.It RekeyLimit
.It RemoteForward
+.It RequestTTY
.It RhostsRSAAuthentication
.It RSAAuthentication
.It SendEnv
@@ -664,7 +667,9 @@ Both protocols support similar authentication methods,
but protocol 2 is the default since
it provides additional mechanisms for confidentiality
(the traffic is encrypted using AES, 3DES, Blowfish, CAST128, or Arcfour)
-and integrity (hmac-md5, hmac-sha1, umac-64, hmac-ripemd160).
+and integrity (hmac-md5, hmac-sha1,
+hmac-sha2-256, hmac-sha2-512,
+umac-64, hmac-ripemd160).
Protocol 1 lacks a strong mechanism for ensuring the
integrity of the connection.
.Pp