summaryrefslogtreecommitdiff
path: root/usr/src/man/man1
diff options
context:
space:
mode:
Diffstat (limited to 'usr/src/man/man1')
-rw-r--r--usr/src/man/man1/Makefile27
-rw-r--r--usr/src/man/man1/scp.sunssh.1234
-rw-r--r--usr/src/man/man1/sftp.sunssh.1592
-rw-r--r--usr/src/man/man1/ssh-add.sunssh.1245
-rw-r--r--usr/src/man/man1/ssh-agent.sunssh.1187
-rw-r--r--usr/src/man/man1/ssh-http-proxy-connect.sunssh.1208
-rw-r--r--usr/src/man/man1/ssh-keygen.sunssh.1409
-rw-r--r--usr/src/man/man1/ssh-keyscan.sunssh.1248
-rw-r--r--usr/src/man/man1/ssh-socks5-proxy-connect.sunssh.1202
-rw-r--r--usr/src/man/man1/ssh.sunssh.1979
10 files changed, 0 insertions, 3331 deletions
diff --git a/usr/src/man/man1/Makefile b/usr/src/man/man1/Makefile
index d5415d5f5c..4f73ebc9ee 100644
--- a/usr/src/man/man1/Makefile
+++ b/usr/src/man/man1/Makefile
@@ -328,7 +328,6 @@ MANFILES= acctcom.1 \
rusers.1 \
rwho.1 \
sar.1 \
- scp.sunssh.1 \
script.1 \
sdiff.1 \
sed.1 \
@@ -337,7 +336,6 @@ MANFILES= acctcom.1 \
setfacl.1 \
setlabel.1 \
setpgrp.1 \
- sftp.sunssh.1 \
shcomp.1 \
shell_builtins.1 \
shift.1 \
@@ -351,13 +349,6 @@ MANFILES= acctcom.1 \
spell.1 \
split.1 \
srchtxt.1 \
- ssh.sunssh.1 \
- ssh-add.sunssh.1 \
- ssh-agent.sunssh.1 \
- ssh-http-proxy-connect.sunssh.1 \
- ssh-keygen.sunssh.1 \
- ssh-keyscan.sunssh.1 \
- ssh-socks5-proxy-connect.sunssh.1 \
strchg.1 \
strings.1 \
strip.1 \
@@ -514,22 +505,13 @@ MANLINKS= batch.1 \
rmail.1 \
rmdir.1 \
rmumount.1 \
- scp.1 \
select.1 \
setenv.1 \
settime.1 \
- sftp.1 \
sh.1 \
snca.1 \
source.1 \
spellin.1 \
- ssh.1 \
- ssh-add.1 \
- ssh-agent.1 \
- ssh-http-proxy-connect.1 \
- ssh-keygen.1 \
- ssh-keyscan.1 \
- ssh-socks5-proxy-connect.1 \
stop.1 \
strconf.1 \
switch.1 \
@@ -717,15 +699,6 @@ hashcheck.1 := LINKSRC = spell.1
hashmake.1 := LINKSRC = spell.1
spellin.1 := LINKSRC = spell.1
-scp.1 := LINKSRC = scp.sunssh.1
-sftp.1 := LINKSRC = sftp.sunssh.1
-ssh.1 := LINKSRC = ssh.sunssh.1
-ssh-add.1 := LINKSRC = ssh-add.sunssh.1
-ssh-agent.1 := LINKSRC = ssh-agent.sunssh.1
-ssh-http-proxy-connect.1 := LINKSRC = ssh-http-proxy-connect.sunssh.1
-ssh-keygen.1 := LINKSRC = ssh-keygen.sunssh.1
-ssh-keyscan.1 := LINKSRC = ssh-keyscan.sunssh.1
-ssh-socks5-proxy-connect.1 := LINKSRC = ssh-socks5-proxy-connect.sunssh.1
strconf.1 := LINKSRC = strchg.1
diff --git a/usr/src/man/man1/scp.sunssh.1 b/usr/src/man/man1/scp.sunssh.1
deleted file mode 100644
index 5e61218d3d..0000000000
--- a/usr/src/man/man1/scp.sunssh.1
+++ /dev/null
@@ -1,234 +0,0 @@
-'\" te
-.\" To view license terms, attribution, and copyright for OpenSSH, the default path is /var/sadm/pkg/SUNWsshdr/install/copyright. If the Solaris operating environment has been installed anywhere other than the default, modify the given path to access the file at the
-.\" installed location.
-.\" Portions Copyright (c) 2007, Sun Microsystems, Inc. All Rights Reserved.
-.TH SCP 1 "Jun 22, 2007"
-.SH NAME
-scp \- secure copy (remote file copy program)
-.SH SYNOPSIS
-.LP
-.nf
-\fBscp\fR [\fB-pqrvBC46\fR] [\fB-F\fR \fIssh_config\fR] [\fB-S\fR \fIprogram\fR] [\fB-P\fR \fIport\fR]
- [\fB-c\fR \fIcipher\fR] [\fB-i\fR \fIidentity_file\fR] [\fB-o\fR \fIssh_option\fR]
- [ [\fIuser\fR@]\fIhost1\fR:]\fIfile1\fR []... [ [\fIuser\fR@]\fIhost2\fR:]\fIfile2\fR
-.fi
-
-.SH DESCRIPTION
-.LP
-The \fBscp\fR utility copies files between hosts on a network. It uses
-\fBssh\fR(1) for data transfer, and uses the same authentication and provides
-the same security as \fBssh\fR(1). Unlike \fBrcp\fR(1), \fBscp\fR will ask for
-passwords or passphrases if they are needed for authentication.
-.sp
-.LP
-Any file name may contain a host and user specification to indicate that the
-file is to be copied to/from that host. Copies between two remote hosts are
-permitted.
-.SH OPTIONS
-.LP
-The following options are supported:
-.sp
-.ne 2
-.na
-\fB\fB-4\fR\fR
-.ad
-.RS 20n
-Forces \fBscp\fR to use IPv4 addresses only.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-6\fR\fR
-.ad
-.RS 20n
-Forces \fBscp\fR to use IPv6 addresses only.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-B\fR\fR
-.ad
-.RS 20n
-Selects batch mode. (Prevents asking for passwords or passphrases.)
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-c\fR \fIcipher\fR\fR
-.ad
-.RS 20n
-Selects the cipher to use for encrypting the data transfer. This option is
-directly passed to \fBssh\fR(1).
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-C\fR\fR
-.ad
-.RS 20n
-Compression enable. Passes the \fB-C\fR flag to \fBssh\fR(1) to enable
-compression.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-F\fR \fIssh_config\fR\fR
-.ad
-.RS 20n
-Specifies an alternative per-user configuration file for \fBssh\fR(1.).
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-i\fR \fIidentity_file\fR\fR
-.ad
-.RS 20n
-Selects the file from which the identity (private key) for \fBRSA\fR
-authentication is read. This option is directly passed to \fBssh\fR(1).
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-o\fR \fIssh_option\fR\fR
-.ad
-.RS 20n
-The given option is directly passed to \fBssh\fR(1).
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-p\fR\fR
-.ad
-.RS 20n
-Preserves modification times, access times, and modes from the original file.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-P\fR \fIport\fR\fR
-.ad
-.RS 20n
-Specifies the port to connect to on the remote host. Notice that this option is
-written with a capital `P', because \fB-p\fR is already reserved for preserving
-the times and modes of the file in \fBrcp\fR(1).
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-q\fR\fR
-.ad
-.RS 20n
-Disables the progress meter.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-r\fR\fR
-.ad
-.RS 20n
-Recursively copies entire directories.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-S\fR \fIprogram\fR\fR
-.ad
-.RS 20n
-Specifies the name of the program to use for the encrypted connection. The
-program must understand \fBssh\fR(1) options.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-v\fR\fR
-.ad
-.RS 20n
-Verbose mode. Causes \fBscp\fR and \fBssh\fR(1) to print debugging messages
-about their progress. This is helpful in debugging connection, authentication,
-and configuration problems.
-.RE
-
-.SH OPERANDS
-.LP
-The following operands are supported:
-.sp
-.ne 2
-.na
-\fB\fIhost1, host2,\fR...\fR
-.ad
-.RS 20n
-The name(s) of the host from or to which the file is to be copied.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fIfile1, file2,\fR...\fR
-.ad
-.RS 20n
-The file(s) to be copied.
-.RE
-
-.SH EXIT STATUS
-.LP
-The following exit values are returned:
-.sp
-.ne 2
-.na
-\fB\fB0\fR\fR
-.ad
-.RS 5n
-Successful completion.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB1\fR\fR
-.ad
-.RS 5n
-An error occurred.
-.RE
-
-.SH ATTRIBUTES
-.LP
-See \fBattributes\fR(5) for descriptions of the following attributes:
-.sp
-
-.sp
-.TS
-box;
-c | c
-l | l .
-ATTRIBUTE TYPE ATTRIBUTE VALUE
-_
-Interface Stability Evolving
-.TE
-
-.SH SEE ALSO
-.LP
-\fBrcp\fR(1), \fBssh\fR(1), \fBssh-add\fR(1), \fBssh-agent\fR(1),
-\fBssh-keygen\fR(1), \fBsshd\fR(1M), \fBssh_config\fR(4), \fBattributes\fR(5)
-.SH NOTES
-.LP
-Generally, use of \fBscp\fR with password or keyboard-interactive
-authentication method and two remote hosts does not work. It does work with
-either the \fBpubkey\fR, \fBhostbased\fR or \fBgssapi-keyex\fR authentication
-method. For the \fBpubkey\fR authentication method, either private keys not
-protected by a passphrase, or an explicit \fBssh\fR agent forwarding have to
-be used. The \fBgssapi-keyex\fR authentication method works with the
-\fBkerberos_v5\fR GSS-API mechanism, but only if the
-\fBGSSAPIDelegateCredentials\fR option is enabled.
diff --git a/usr/src/man/man1/sftp.sunssh.1 b/usr/src/man/man1/sftp.sunssh.1
deleted file mode 100644
index 3e7a285660..0000000000
--- a/usr/src/man/man1/sftp.sunssh.1
+++ /dev/null
@@ -1,592 +0,0 @@
-'\" te
-.\" To view license terms, attribution, and copyright for OpenSSH, the default path is /var/sadm/pkg/SUNWsshdr/install/copyright. If the Solaris operating environment has been installed anywhere other than the default, modify the specified path to access
-.\" the file at the installed location.
-.\" Portions Copyright (c) 2007, Sun Microsystems, Inc. All Rights Reserved.
-.TH SFTP 1 "Nov 8, 2007"
-.SH NAME
-sftp \- secure file transfer program
-.SH SYNOPSIS
-.LP
-.nf
-\fBsftp\fR [\fB-1Cv\fR] [\fB-B\fR \fIbuffer_size\fR] [\fB-b\fR \fIbatchfile\fR] [\fB-F\fR \fIssh_config\fR]
- [\fB-o\fR \fIssh_option\fR] [\fB-P\fR \fIsftp_server_path\fR] [\fB-R\fR \fInum_requests\fR]
- [\fB-S\fR \fIprogram\fR] [\fB-s\fR \fIsubsystem\fR | \fIsftp_server\fR] \fIhost\fR
-.fi
-
-.LP
-.nf
-\fBsftp\fR [[\fIuser\fR\fB@\fR]\fIhost\fR[\fB:\fR\fIfile\fR [\fIfile\fR]]]
-.fi
-
-.LP
-.nf
-\fBsftp\fR [[\fIuser\fR\fB@\fR]\fIhost\fR[:\fIdir\fR[\fB/\fR]]]
-.fi
-
-.LP
-.nf
-\fBsftp\fR \fB-b\fR \fIbatchfile\fR [\fIuser\fR\fB@\fR]\fIhost\fR
-.fi
-
-.SH DESCRIPTION
-.LP
-The \fBsftp\fR utility is an interactive file transfer program with a user
-interface similar to \fBftp\fR(1) that uses the \fBssh\fR(1) command to create
-a secure connection to the server.
-.sp
-.LP
-\fBsftp\fR implements the SSH File Transfer Protocol as defined in IETF
-\fBdraft-ietf-secsh-filexfer\fR. There is no relationship between the protocol
-used by \fBsftp\fR and the FTP protocol (\fIRFC 959\fR) provided by
-\fBftp\fR(1).
-.sp
-.LP
-The first usage format causes \fBsftp\fR to connect to the specified host and
-enter an interactive mode. If a username was provided then \fBsftp\fR tries to
-log in as the specified user. If a directory is provided then \fBsftp\fR tries
-to change the current directory on the server to the specified directory before
-entering the interactive mode.
-.sp
-.LP
-The second usage format retrieves the specified file from the server and copies
-it to the specified target file or directory on the client. If a username is
-specified \fBsftp\fR tries to log in as the specified user.
-.SH OPTIONS
-.LP
-The following options are supported:
-.sp
-.ne 2
-.na
-\fB\fB-b\fR \fIbatchfile\fR\fR
-.ad
-.RS 30n
-Batch mode reads a series of commands from an input \fIbatchfile\fR instead of
-\fBstdin\fR. Since it lacks user interaction, it should be used in conjunction
-with non-interactive authentication. A batchfile of \fB-\fR can be used to
-indicate standard input. \fBsftp\fR aborts if any of the following commands
-fail: \fBget\fR, \fBput\fR, \fBrm\fR, \fBrename\fR, \fBln\fR, \fBrm\fR,
-\fBmkdir\fR, \fBchdir\fR, \fBls\fR, \fBlchdir\fR, \fBchmod\fR, \fBchown\fR,
-\fBchgrp\fR, \fBlpwd\fR, and \fBlmkdir\fR. Termination on error can be
-suppressed on a command by command basis by prefixing the command with a
-\fB-\fR character (for example, \fB-rm /tmp/blah*\fR).
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-B\fR \fIbuffer_size\fR\fR
-.ad
-.RS 30n
-Specifies the size of the buffer that \fBsftp\fR uses when transferring files.
-Larger buffers require fewer round trips at the cost of higher memory
-consumption. The default is 32768 bytes.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-C\fR\fR
-.ad
-.RS 30n
-Enables compression, using the \fB-C\fR flag in \fBssh\fR(1).
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-F\fR \fIssh_config\fR\fR
-.ad
-.RS 30n
-Specifies an alternative per-user configuration file for \fBssh\fR. This option
-is directly passed to \fBssh\fR(1).
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-o\fR \fIssh_option\fR\fR
-.ad
-.RS 30n
-Specifies an option to be directly passed to \fBssh\fR(1).
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-P\fR \fIsftp_server path\fR\fR
-.ad
-.RS 30n
-Executes the specified path as an \fIsftp-server\fR and uses a pipe, rather
-than an \fBssh\fR connection, to communicate with it. This option can be useful
-in debugging the \fBsftp\fR client and server. The \fB-P\fR and \fB-S\fR
-options are mutually exclusive.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-R\fR \fInum_requests\fR\fR
-.ad
-.RS 30n
-Specifies how many requests can be outstanding at any one time. Increasing this
-can slightly improve file transfer speed but increases memory usage. The
-default is 16 outstanding requests.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-s\fR \fIsubsystem\fR | \fIsftp_server\fR\fR
-.ad
-.RS 30n
-Specifies the \fBSSH2\fR subsystem or the path for an \fBsftp\fR server on the
-remote host. A path is useful for using \fBsftp\fR over protocol version 1, or
-when the remote \fBsshd\fR does not have an \fBsftp\fR subsystem configured.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-S\fR \fIssh_program\fR \fIpath\fR\fR
-.ad
-.RS 30n
-Uses the specified program instead of \fBssh\fR(1) to connect to the \fBsftp\fR
-server. The \fB-P\fR and \fB-S\fR options are mutually exclusive. The program
-must understand \fBssh\fR(1) options.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-v\fR\fR
-.ad
-.RS 30n
-Raises logging level. This option is also passed to \fBssh\fR(1).
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-1\fR\fR
-.ad
-.RS 30n
-Specifies the use of protocol version 1.
-.RE
-
-.SH OPERANDS
-.LP
-The following operands are supported:
-.sp
-.ne 2
-.na
-\fB\fIhostname\fR | \fIuser@hostname\fR\fR
-.ad
-.RS 28n
-The name of the host to which \fBsftp\fR connects and logs into.
-.RE
-
-.SH INTERACTIVE COMMANDS
-.LP
-Once in interactive mode, \fBsftp\fR understands a set of commands similar to
-those of \fBftp\fR(1). Commands are case insensitive and path names can be
-enclosed in quotes if they contain spaces.
-.sp
-.ne 2
-.na
-\fB\fBbye\fR\fR
-.ad
-.sp .6
-.RS 4n
-Quits \fBsftp\fR.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fBcd\fR \fIpath\fR\fR
-.ad
-.sp .6
-.RS 4n
-Changes remote directory to \fIpath\fR.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fBchgrp\fR \fIgrp path\fR\fR
-.ad
-.sp .6
-.RS 4n
-Changes group of file \fIpath\fR to \fIgrp\fR. \fIgrp\fR must be a numeric
-\fBGID\fR.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fBchmod\fR \fImode path\fR\fR
-.ad
-.sp .6
-.RS 4n
-Changes permissions of file \fIpath\fR to \fImode\fR.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fBchown\fR \fIown path\fR\fR
-.ad
-.sp .6
-.RS 4n
-Changes owner of file \fIpath\fR to \fIown\fR. \fIown\fR must be a numeric
-\fBUID\fR.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fBexit\fR\fR
-.ad
-.sp .6
-.RS 4n
-Quits \fBsftp\fR.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fBget\fR [\fIflags\fR] \fIremote-path\fR [\fIlocal-path\fR]\fR
-.ad
-.sp .6
-.RS 4n
-Retrieves the \fIremote-path\fR and stores it on the local machine. If the
-local path name is not specified, it is specified the same name it has on the
-remote machine. If the \fB-P\fR flag is specified, then the file's full
-permission and access time are copied too.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fBhelp\fR\fR
-.ad
-.sp .6
-.RS 4n
-Displays help text.
-.sp
-Identical to the \fB?\fR command.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fBlcd\fR \fIpath\fR\fR
-.ad
-.sp .6
-.RS 4n
-Changes local directory to \fIpath\fR.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fBlls\fR [\fIls-options\fR [\fIpath\fR]]\fR
-.ad
-.sp .6
-.RS 4n
-Displays local directory listing of either \fIpath\fR or current directory if
-\fIpath\fR is not specified.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fBlmkdir\fR \fIpath\fR\fR
-.ad
-.sp .6
-.RS 4n
-Creates local directory specified by \fIpath\fR.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fBln\fR \fIoldpath\fR \fInewpath\fR\fR
-.ad
-.sp .6
-.RS 4n
-Creates a link from \fIoldpath\fR to \fInewpath\fR.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fBlpwd\fR\fR
-.ad
-.sp .6
-.RS 4n
-Prints local working directory.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fBls\fR [\fB-1aflnrSt\fR] [\fIpath\fR]\fR
-.ad
-.sp .6
-.RS 4n
-Displays remote directory listing of either \fIpath\fR or current directory if
-\fIpath\fR is not specified. \fIpath\fR can contain wildcards.
-.sp
-The \fBls\fR supports the following options:
-.sp
-.ne 2
-.na
-\fB\fB-a\fR\fR
-.ad
-.RS 6n
-Lists files beginning with a dot (\fB\&.\fR).
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-f\fR\fR
-.ad
-.RS 6n
-Does not sort the listing. The default sort order is lexicographical.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-l\fR\fR
-.ad
-.RS 6n
-Displays additional details including permissions and ownership information.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-n\fR\fR
-.ad
-.RS 6n
-Produces a long listing with user and group information presented numerically.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-r\fR\fR
-.ad
-.RS 6n
-Reverses the sort order of the listing.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-S\fR\fR
-.ad
-.RS 6n
-Sorts the listing by file size.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-t\fR\fR
-.ad
-.RS 6n
-Sorts the listing by last modification time.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-1\fR\fR
-.ad
-.RS 6n
-Produces single column output.
-.RE
-
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fBlumask\fR \fIumask\fR\fR
-.ad
-.sp .6
-.RS 4n
-Sets local \fBumask\fR to \fIumask\fR.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fBmkdir\fR \fIpath\fR\fR
-.ad
-.sp .6
-.RS 4n
-Creates remote directory specified by \fIpath\fR.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fBput\fR [\fIflags\fR] \fIlocal-path\fR [\fIlocal-path\fR]\fR
-.ad
-.sp .6
-.RS 4n
-Uploads \fIlocal-path\fR and stores it on the remote machine. If the remote
-path name is not specified, it is specified the same name it has on the local
-machine. If the \fB-P\fR flag is specified, then the file's full permission and
-access time are copied too.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fBpwd\fR\fR
-.ad
-.sp .6
-.RS 4n
-Displays remote working directory.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fBquit\fR\fR
-.ad
-.sp .6
-.RS 4n
-Quits \fBsftp\fR.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fBrename\fR \fIoldpath newpath\fR\fR
-.ad
-.sp .6
-.RS 4n
-Renames remote file from \fIoldpath\fR to \fInewpath\fR.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fBrm\fR \fIpath\fR\fR
-.ad
-.sp .6
-.RS 4n
-Deletes remote file specified by \fIpath\fR.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fBrmdir\fR \fIpath\fR\fR
-.ad
-.sp .6
-.RS 4n
-Removes remote directory specified by \fIpath\fR.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fBsymlink\fR \fIoldpath\fR \fInewpath\fR\fR
-.ad
-.sp .6
-.RS 4n
-Creates a symbolic link from \fIoldpath\fR to \fInewpath\fR.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fBversion\fR\fR
-.ad
-.sp .6
-.RS 4n
-Displays the \fBsftp\fR protocol version.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB#\fR [\fIcomment\fR]\fR
-.ad
-.sp .6
-.RS 4n
-Include a comment. This is useful in batch files.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB!\fR [\fIcommand\fR]\fR
-.ad
-.sp .6
-.RS 4n
-If \fIcommand\fR is not specified, escapes to the local shell.
-.sp
-If \fIcommand\fR is specified, executes \fIcommand\fR in the local shell.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB?\fR\fR
-.ad
-.sp .6
-.RS 4n
-Displays help text.
-.sp
-Identical to the \fBhelp\fR command.
-.RE
-
-.SH EXIT STATUS
-.LP
-The following exit values are returned:
-.sp
-.ne 2
-.na
-\fB\fB0\fR\fR
-.ad
-.RS 6n
-Successful completion.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB>0\fR\fR
-.ad
-.RS 6n
-An error occurred.
-.RE
-
-.SH ATTRIBUTES
-.LP
-See \fBattributes\fR(5) for descriptions of the following attributes:
-.sp
-
-.sp
-.TS
-box;
-c | c
-l | l .
-ATTRIBUTE TYPE ATTRIBUTE VALUE
-_
-Interface Stability Committed
-.TE
-
-.SH SEE ALSO
-.LP
-\fBftp\fR(1), \fBscp\fR(1), \fBssh\fR(1), \fBssh-add\fR(1),
-\fBssh-keygen\fR(1), \fBsshd\fR(1M), \fBattributes\fR(5)
diff --git a/usr/src/man/man1/ssh-add.sunssh.1 b/usr/src/man/man1/ssh-add.sunssh.1
deleted file mode 100644
index 7de85f56fa..0000000000
--- a/usr/src/man/man1/ssh-add.sunssh.1
+++ /dev/null
@@ -1,245 +0,0 @@
-'\" te
-.\" To view license terms, attribution, and copyright for OpenSSH, the default path is /var/sadm/pkg/SUNWsshdr/install/copyright. If the Solaris operating environment has been installed anywhere other than the default, modify the given path to access the file at the
-.\" installed location.
-.\" Portions Copyright (c) 2009, Sun Microsystems, Inc. All Rights Reserved.
-.TH SSH-ADD 1 "May 20, 2009"
-.SH NAME
-ssh-add \- add RSA or DSA identities to the authentication agent
-.SH SYNOPSIS
-.LP
-.nf
-\fBssh-add\fR [\fB-lLdDxX\fR] [\fB-t\fR \fIlife\fR] [ \fIfile\fR ]...
-.fi
-
-.SH DESCRIPTION
-.LP
-The \fBssh-add\fR utility adds \fBRSA\fR or \fBDSA\fR identities to the
-authentication agent, \fBssh-agent\fR(1). When run without arguments, it
-attempts to add all of the files \fB$HOME/.ssh/identity\fR (RSA v1),
-\fB$HOME/.ssh/id_rsa\fR (RSA v2), and \fB$HOME/.ssh/id_dsa\fR (DSA v2) that
-exist. If more than one of the private keys exists, an attempt to decrypt each
-with the same passphrase is made before reprompting for a different passphrase.
-The passphrase is read from the user's tty or by running the program defined in
-\fBSSH_ASKPASS\fR (see below).
-.sp
-.LP
-The authentication agent must be running.
-.SH OPTIONS
-.LP
-The following options are supported:
-.sp
-.ne 2
-.na
-\fB\fB-d\fR\fR
-.ad
-.RS 11n
-Instead of adding the identity, this option \fBremoves\fR the identity from the
-agent.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-D\fR\fR
-.ad
-.RS 11n
-Deletes all identities from the agent.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-l\fR\fR
-.ad
-.RS 11n
-Lists fingerprints of all identities currently represented by the agent.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-L\fR\fR
-.ad
-.RS 11n
-Lists public key parameters of all identities currently represented by the
-agent.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-t\fR \fIlife\fR\fR
-.ad
-.RS 11n
-Sets a maximum lifetime when adding identities to an agent. The lifetime can be
-specified in seconds or in a time format specified in \fBsshd\fR(1M).
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-x\fR\fR
-.ad
-.RS 11n
-Locks the agent with a password.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-X\fR\fR
-.ad
-.RS 11n
-Unlocks the agent.
-.RE
-
-.SH ENVIRONMENT VARIABLES
-.ne 2
-.na
-\fB\fBDISPLAY\fR\fR
-.ad
-.br
-.na
-\fB\fBSSH_ASKPASS\fR\fR
-.ad
-.RS 17n
-If \fBssh-add\fR needs a passphrase, it reads the passphrase from the current
-terminal if it was run from a terminal. If \fBssh-add\fR does not have a
-terminal associated with it but \fBDISPLAY\fR and \fBSSH_ASKPASS\fR are set, it
-executes the program specified by \fBSSH_ASKPASS\fR and open an X11 window to
-read the passphrase. This is particularly useful when calling \fBssh-add\fR
-from a .Xsession or related script. The system is shipped with
-\fB/usr/lib/ssh/ssh-askpass\fR which is the default value for
-\fBSSH_ASKPASS\fR.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fBSSH_AUTH_SOCK\fR\fR
-.ad
-.RS 17n
-Identifies the path of a unix-domain socket used to communicate with the agent.
-.RE
-
-.SH EXIT STATUS
-.LP
-The following exit values are returned:
-.sp
-.ne 2
-.na
-\fB\fB0\fR\fR
-.ad
-.RS 5n
-Successful completion.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB1\fR\fR
-.ad
-.RS 5n
-An error occurred.
-.RE
-
-.SH FILES
-.LP
-These files should not be readable by anyone but the user. Notice that
-\fBssh-add\fR ignores a file if it is accessible by others. It is possible to
-specify a passphrase when generating the key; that passphrase is used to
-encrypt the private part of this file.
-.sp
-.LP
-If these files are stored on a network file system it is assumed that either
-the protection provided in the file themselves or the transport layer of the
-network file system provides sufficient protection for the site policy. If this
-is not the case, then it is recommended the key files are stored on removable
-media or locally on the relevant hosts.
-.sp
-.LP
-Recommended names for the \fBDSA\fR and \fBRSA\fR key files:
-.sp
-.ne 2
-.na
-\fB\fB$HOME/.ssh/identity\fR\fR
-.ad
-.RS 28n
-Contains the \fBRSA\fR authentication identity of the user for protocol version
-1.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB$HOME/.ssh/identity.pub\fR\fR
-.ad
-.RS 28n
-Contains the public part of the \fBRSA\fR authentication identity of the user
-for protocol version 1.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB$HOME/.ssh/id_dsa\fR\fR
-.ad
-.RS 28n
-Contains the private \fBDSA\fR authentication identity of the user.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB$HOME/.ssh/id_dsa.pub\fR\fR
-.ad
-.RS 28n
-Contains the public part of the DSA authentication identity of the user.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB$HOME/.ssh/id_rsa\fR\fR
-.ad
-.RS 28n
-Contains the private \fBRSA\fR authentication identity of the user.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB$HOME/.ssh/id_rsa.pub\fR\fR
-.ad
-.RS 28n
-Contains the public part of the \fBRSA\fR authentication identity of the user.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB/usr/lib/ssh/ssh-askpass\fR\fR
-.ad
-.RS 28n
-Contains the default value for SSH_ASKPASS.
-.RE
-
-.SH ATTRIBUTES
-.LP
-See \fBattributes\fR(5) for descriptions of the following attributes:
-.sp
-
-.sp
-.TS
-box;
-c | c
-l | l .
-ATTRIBUTE TYPE ATTRIBUTE VALUE
-_
-Interface Stability Committed
-.TE
-
-.SH SEE ALSO
-.LP
-\fBssh\fR(1), \fBssh-agent\fR(1), \fBssh-keygen\fR(1), \fBsshd\fR(1M),
-\fBattributes\fR(5)
diff --git a/usr/src/man/man1/ssh-agent.sunssh.1 b/usr/src/man/man1/ssh-agent.sunssh.1
deleted file mode 100644
index cabafb3e59..0000000000
--- a/usr/src/man/man1/ssh-agent.sunssh.1
+++ /dev/null
@@ -1,187 +0,0 @@
-'\" te
-.\" To view license terms, attribution, and copyright for OpenSSH, the default path is /var/sadm/pkg/SUNWsshdr/install/copyright. If the Solaris operating environment has been installed anywhere other than the default, modify the given path to access the file at the
-.\" installed location.
-.\" Portions Copyright (c) 2009, Sun Microsystems, Inc. All Rights Reserved.
-.TH SSH-AGENT 1 "Aug 17, 2009"
-.SH NAME
-ssh-agent \- authentication agent
-.SH SYNOPSIS
-.LP
-.nf
-\fBssh-agent\fR [\fB-a\fR \fIbind_address\fR] [\fB-c\fR | \fB-s\fR ] [\fB-d\fR]
- [-t \fIlife\fR] [\fIcommand\fR [\fIargs\fR]...]
-.fi
-
-.LP
-.nf
-\fBssh-agent\fR [\fB-c\fR | \fB-s\fR] \fB-k\fR
-.fi
-
-.SH DESCRIPTION
-.LP
-\fBssh-agent\fR is a program to hold private keys used for public key
-authentication (\fBRSA\fR, \fBDSA\fR). \fBssh-agent\fR is often started at the
-beginning of a login session. All other windows or programs are started as
-clients to the \fBssh-agent\fR program. Through use of environment variables,
-the agent can be located and automatically used for authentication when logging
-in to other machines using \fBssh\fR(1). See the \fISystem Administration
-Guide: Security Services\fR.
-.sp
-.LP
-If a command line is given, this is executed as a subprocess of the agent. When
-the command dies, so does the agent.
-.sp
-.LP
-The agent initially does not have any private keys. Keys are added using
-\fBssh-add\fR(1), which sends the identity to the agent. Several identities can
-be stored in the agent; the agent can automatically use any of these
-identities. Use the \fB-l\fR option in \fBssh-add\fR(1) to display the
-identities currently held by the agent.
-.sp
-.LP
-The agent is run in the user's local host. Authentication data need not be
-stored on any other machine, and authentication passphrases never go over the
-network. However, if the connection to the agent is forwarded over \fBSSH\fR
-remote logins, the user can use the privileges given by the identities anywhere
-in the network in a secure way.
-.sp
-.LP
-There are two main ways to get an agent setup. Either you let the agent start a
-new subcommand into which some environment variables are exported, or you let
-the agent print the needed shell commands (either \fBsh\fR(1) or \fBcsh\fR(1)
-syntax can be generated) which can be evalled in the calling shell. Later, use
-\fBssh\fR(1) to look at these variables and use them to establish a connection
-to the agent.
-.sp
-.LP
-A unix-domain socket is created (\fB/tmp/ssh-XXXXXXXX/agent.\fIpid\fR\fR) and
-the name of this socket is stored in the \fBSSH_AUTH_SOCK\fR environment
-variable. The socket is made accessible only to the current user. This method
-is easily abused by root or another instance of the same user.
-.sp
-.LP
-The \fBSSH_AGENT_PID\fR environment variable holds the agent's \fBPID\fR.
-.sp
-.LP
-The agent exits automatically when the command given on the command line
-terminates.
-.SH OPTIONS
-.LP
-The following options are supported:
-.sp
-.ne 2
-.na
-\fB\fB-a\fR \fIbind_address\fR\fR
-.ad
-.RS 19n
-Binds the agent to the unix-domain socket bind_address. The default is
-\fB/tmp/ssh-XXXXXXXX/agent.\fIpid\fR\fR.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-c\fR\fR
-.ad
-.RS 19n
-Generates C-shell commands on stdout. This is the default if \fBSHELL\fR
-indicates that it is a csh style of shell.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-d\fR\fR
-.ad
-.RS 19n
-Debug mode. When this option is specified, \fBssh-agent\fR does not fork.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-k\fR\fR
-.ad
-.RS 19n
-Kills the current agent (given by the \fBSSH_AGENT_PID\fR environment
-variable).
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-s\fR\fR
-.ad
-.RS 19n
-Generates Bourne shell commands on stdout. This is the default if \fBSHELL\fR
-does not indicate that it is a csh style of shell.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-t\fR \fIlife\fR\fR
-.ad
-.RS 19n
-Set a default value for the maximum lifetime (\fIlife\fR) of identities added
-to the agent. \fIlife\fR can be specified in seconds or in a time format
-specified in \fBsshd_config\fR(4). \fIlife\fR specified for an identity with
-\fBssh-add\fR(1) overrides this value. Without this option the default maximum
-\fIlife\fR is forever.
-.RE
-
-.SH EXIT STATUS
-.LP
-The following exit values are returned:
-.sp
-.ne 2
-.na
-\fB\fB0\fR\fR
-.ad
-.RS 5n
-Successful completion.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB1\fR\fR
-.ad
-.RS 5n
-An error occurred.
-.RE
-
-.SH FILES
-.ne 2
-.na
-\fB\fB/tmp/ssh-XXXXXXXX/agent.\fIpid\fR\fR\fR
-.ad
-.sp .6
-.RS 4n
-Unix-domain sockets used to contain the connection to the authentication agent.
-These sockets should only be readable by the owner. The sockets are removed
-when the agent exits.
-.RE
-
-.SH ATTRIBUTES
-.LP
-See \fBattributes\fR(5) for descriptions of the following attributes:
-.sp
-
-.sp
-.TS
-box;
-c | c
-l | l .
-ATTRIBUTE TYPE ATTRIBUTE VALUE
-_
-Interface Stability Committed
-.TE
-
-.SH SEE ALSO
-.LP
-\fBssh\fR(1), \fBssh-add\fR(1), \fBssh-keygen\fR(1), \fBsshd\fR(1M),
-\fBsshd_config\fR(4), \fBattributes\fR(5)
-.sp
-.LP
-\fISystem Administration Guide: Security Services\fR
diff --git a/usr/src/man/man1/ssh-http-proxy-connect.sunssh.1 b/usr/src/man/man1/ssh-http-proxy-connect.sunssh.1
deleted file mode 100644
index a12395ccb4..0000000000
--- a/usr/src/man/man1/ssh-http-proxy-connect.sunssh.1
+++ /dev/null
@@ -1,208 +0,0 @@
-'\" te
-.\" Copyright (c) 2001, Sun Microsystems, Inc. All Rights Reserved
-.\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
-.\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
-.\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
-.TH SSH-HTTP-PROXY-CONNECT 1 "Oct 24, 2001"
-.SH NAME
-ssh-http-proxy-connect \- Secure Shell proxy for HTTP
-.SH SYNOPSIS
-.LP
-.nf
-\fB/usr/lib/ssh/ssh-http-proxy-connect\fR [\fB-h\fR \fIhttp_proxy_host\fR]
- [\fB-p\fR \fIhttp_proxy_port\fR] \fIconnect_host\fR \fIconnect_port\fR
-.fi
-
-.SH DESCRIPTION
-.LP
-A proxy command for \fBssh\fR(1) that uses HTTP CONNECT. Typical use is where
-connections external to a network are only allowed via a proxy web server.
-.SH OPTIONS
-.LP
-The following options are supported:
-.sp
-.ne 2
-.na
-\fB\fB-h\fR \fIhttp_proxy_host\fR\fR
-.ad
-.RS 22n
-Specifies the proxy web server through which to connect. Overrides the
-\fBHTTPPROXY\fR and \fBhttp_proxy\fR environment variables if they are set.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-p\fR \fIhttp_proxy_port\fR\fR
-.ad
-.RS 22n
-Specifies the port on which the proxy web server runs. If not specified, port
-80 is assumed. Overrides the \fBHTTPPROXYPORT\fR and \fBhttp_proxy\fR
-environment variables if they are set.
-.RE
-
-.SH OPERANDS
-.LP
-The following operands are supported:
-.sp
-.ne 2
-.na
-\fB\fIhttp_proxy_host\fR\fR
-.ad
-.RS 19n
-The host name or IP address (IPv4 or IPv6) of the proxy.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fIhttp_proxy_port\fR\fR
-.ad
-.RS 19n
-The numeric port number to connect to on \fIhttp_proxy_host\fR.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fIconnect_host\fR\fR
-.ad
-.RS 19n
-The name of the remote host to which the proxy web server is to connect you.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fIconnect_port\fR\fR
-.ad
-.RS 19n
-The numeric port number of the proxy web server to connect you to on
-\fIhttp_proxy_host\fR.
-.RE
-
-.SH EXAMPLES
-.LP
-The recommended way to use a proxy connection command is to configure the
-\fBProxyCommand\fR in \fBssh_config\fR(4) (see Example 1 and Example 2).
-Example 3 shows how the proxy command can be specified on the command line when
-running \fBssh\fR(1).
-.LP
-\fBExample 1 \fRSetting the proxy from the environment
-.sp
-.LP
-The following example uses \fBssh-http-proxy-connect\fR in \fBssh_config\fR(4)
-when the proxy is set from the environment:
-
-.sp
-.in +2
-.nf
-\fBHost playtime.foo.com
- ProxyCommand /usr/lib/ssh/ssh-http-proxy-connect \e
- playtime.foo.com 22\fR
-.fi
-.in -2
-.sp
-
-.LP
-\fBExample 2 \fROverriding proxy environment variables
-.sp
-.LP
-The following example uses \fBssh-http-proxy-connect\fR in \fBssh_config\fR(4)
-to override (or if not set) proxy environment variables:
-
-.sp
-.in +2
-.nf
-\fBHost playtime.foo.com
- ProxyCommand /usr/lib/ssh/ssh-http-proxy-connect -h webcache \e
- -p 8080 playtime.foo.com 22\fR
-.fi
-.in -2
-.sp
-
-.LP
-\fBExample 3 \fRUsing the command line
-.sp
-.LP
-The following example uses \fBssh-http-proxy-connect\fR from the \fBssh\fR(1)
-command line:
-
-.sp
-.in +2
-.nf
-example$ \fBssh -o'ProxyCommand="/usr/lib/ssh/ssh-http-proxy-connect \e
- -h webcache -p 8080 playtime.foo.com 22"' playtime.foo.com\fR
-.fi
-.in -2
-.sp
-
-.SH ENVIRONMENT VARIABLES
-.ne 2
-.na
-\fB\fBHTTPPROXY\fR\fR
-.ad
-.RS 17n
-Takes the \fIhttp_proxy_host\fR operand to specify the default proxy host.
-Overrides \fBhttp_proxy\fR if both are set.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fBHTTPPROXYPORT\fR\fR
-.ad
-.RS 17n
-Takes the \fIhttp_proxy_port\fR operand to specify the default proxy port.
-Ignored if \fBHTTPPROXY\fR is not set.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fBhttp_proxy\fR\fR
-.ad
-.RS 17n
-\fBURL\fR format for specifying proxy host and port.
-.RE
-
-.SH EXIT STATUS
-.LP
-The following exit values are returned:
-.sp
-.ne 2
-.na
-\fB\fB0\fR \fR
-.ad
-.RS 6n
-Successful completion.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB1\fR \fR
-.ad
-.RS 6n
-An error occurred.
-.RE
-
-.SH ATTRIBUTES
-.LP
-See \fBattributes\fR(5) for descriptions of the following attributes:
-.sp
-
-.sp
-.TS
-box;
-c | c
-l | l .
-ATTRIBUTE TYPE ATTRIBUTE VALUE
-_
-Interface Stability Stable
-.TE
-
-.SH SEE ALSO
-.LP
-\fBssh\fR(1), \fBssh-socks5-proxy-connect\fR(1), \fBssh_config\fR(4),
-\fBattributes\fR(5)
diff --git a/usr/src/man/man1/ssh-keygen.sunssh.1 b/usr/src/man/man1/ssh-keygen.sunssh.1
deleted file mode 100644
index 7468f97e7f..0000000000
--- a/usr/src/man/man1/ssh-keygen.sunssh.1
+++ /dev/null
@@ -1,409 +0,0 @@
-'\" te
-.\" To view license terms, attribution, and copyright for OpenSSH, the default path is /var/sadm/pkg/SUNWsshdr/install/copyright. If the Solaris operating environment has been installed anywhere other than the default, modify the given path to access the file at the
-.\" installed location.
-.\" Portions Copyright (c) 2009, Sun Microsystems, Inc. All Rights Reserved.
-.TH SSH-KEYGEN 1 "Feb 17, 2009"
-.SH NAME
-ssh-keygen \- authentication key generation
-.SH SYNOPSIS
-.LP
-.nf
-\fBssh-keygen\fR [\fB-q\fR] [\fB-b\fR \fIbits\fR ] \fB-t\fR \fItype\fR [\fB-N\fR \fInew_passphrase\fR]
- [\fB-C\fR \fIcomment\fR] [\fB-f\fR \fIoutput_keyfile\fR]
-.fi
-
-.LP
-.nf
-\fBssh-keygen\fR \fB-p\fR [\fB-P\fR \fIold_passphrase\fR] [\fB-N\fR \fInew_passphrase\fR]
- [\fB-f\fR \fIkeyfile\fR]
-.fi
-
-.LP
-.nf
-\fBssh-keygen\fR \fB-i\fR [\fB-f\fR \fIinput_keyfile\fR]
-.fi
-
-.LP
-.nf
-\fBssh-keygen\fR \fB-e\fR [\fB-f\fR \fIinput_keyfile\fR]
-.fi
-
-.LP
-.nf
-\fBssh-keygen\fR \fB-y\fR [\fB-f\fR \fIinput_keyfile\fR]
-.fi
-
-.LP
-.nf
-\fBssh-keygen\fR \fB-c\fR [\fB-P\fR \fIpassphrase\fR] [\fB-C\fR \fIcomment\fR] [\fB-f\fR \fIkeyfile\fR]
-.fi
-
-.LP
-.nf
-\fBssh-keygen\fR \fB-l\fR [\fB-f\fR \fIinput_keyfile\fR]
-.fi
-
-.LP
-.nf
-\fBssh-keygen\fR \fB-B\fR [\fB-f\fR \fIinput_keyfile\fR]
-.fi
-
-.LP
-.nf
-\fBssh-keygen\fR \fB-F\fR \fIhostname\fR [\fB-f\fR \fIknown_hosts_file\fR]
-.fi
-
-.LP
-.nf
-\fBssh-keygen\fR \fB-H\fR [\fB-f\fR \fIknown_hosts_file\fR]
-.fi
-
-.LP
-.nf
-\fBssh-keygen\fR \fB-R\fR \fIhostname\fR [\fB-f\fR \fIknown_hosts_file\fR]
-.fi
-
-.SH DESCRIPTION
-.LP
-The \fBssh-keygen\fR utility generates, manages, and converts authentication
-keys for \fBssh\fR(1). \fBssh-keygen\fR can create RSA keys for use by SSH
-protocol version 1 and RSA or DSA keys for use by SSH protocol version 2. The
-type of key to be generated is specified with the \fB-t\fR option.
-.sp
-.LP
-Normally, each user wishing to use \fBSSH\fR with \fBRSA\fR or \fBDSA\fR
-authentication runs this once to create the authentication key in
-\fB$HOME/.ssh/identity\fR, \fB$HOME/.ssh/id_dsa\fR, or \fB$HOME/.ssh/id_rsa\fR.
-The system administrator can also use this to generate host keys..
-.sp
-.LP
-Ordinarily, this program generates the key and asks for a file in which to
-store the private key. The public key is stored in a file with the same name
-but with the ``\fB\&.pub\fR'' extension appended. The program also asks for a
-passphrase. The passphrase can be empty to indicate no passphrase (host keys
-must have empty passphrases), or it can be a string of arbitrary length. Good
-passphrases are 10-30 characters long, are not simple sentences or otherwise
-easy to guess, and contain a mix of uppercase and lowercase letters, numbers,
-and non-alphanumeric characters. (English prose has only 1-2 bits of entropy
-per word and provides very poor passphrases.) If a passphrase is set, it must
-be at least 4 characters long.
-.sp
-.LP
-The passphrase can be changed later by using the \fB-p\fR option.
-.sp
-.LP
-There is no way to recover a lost passphrase. If the passphrase is lost or
-forgotten, you have to generate a new key and copy the corresponding public key
-to other machines.
-.sp
-.LP
-For \fBRSA\fR, there is also a comment field in the key file that is only for
-convenience to the user to help identify the key. The \fIcomment\fR can tell
-what the key is for, or whatever is useful. The comment is initialized to
-``\fBuser@host\fR'' when the key is created, but can be changed using the
-\fB-c\fR option.
-.sp
-.LP
-After a key is generated, instructions below detail where to place the keys to
-activate them.
-.SH OPTIONS
-.LP
-The following options are supported:
-.sp
-.ne 2
-.na
-\fB\fB-b\fR \fIbits\fR\fR
-.ad
-.RS 21n
-Specifies the number of bits in the key to create. The minimum number is 512
-bits. Generally, 1024 bits is considered sufficient. Key sizes above that no
-longer improve security but make things slower. The default is 1024 bits.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-B\fR\fR
-.ad
-.RS 21n
-Shows the bubblebabble digest of the specified private or public key file.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-c\fR\fR
-.ad
-.RS 21n
-Requests changing the comment in the private and public key files. The program
-prompts for the file containing the private keys, for the passphrase if the key
-has one, and for the new comment.
-.sp
-This option only applies to \fBrsa1\fR (\fBSSHv1\fR) keys.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-C\fR \fIcomment\fR\fR
-.ad
-.RS 21n
-Provides the new comment.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-e\fR\fR
-.ad
-.RS 21n
-This option reads a private or public OpenSSH key file and prints the key in a
-"SECSH" Public Key File Format to stdout. This option allows exporting keys for
-use by several other SSH implementations.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-f\fR\fR
-.ad
-.RS 21n
-Specifies the filename of the key file.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-F\fR\fR
-.ad
-.RS 21n
-Search for the specified \fIhostname\fR in a \fBknown_hosts\fR file, listing
-any occurrences found. This option is useful to find hashed host names or
-addresses and can also be used in conjunction with the \fB-H\fR option to print
-found keys in a hashed format.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-H\fR\fR
-.ad
-.RS 21n
-Hash a \fBknown_hosts\fR file. This replaces all host names and addresses with
-hashed representations within the specified file. The original content is moved
-to a file with a \fB\&.old\fR suffix. These hashes may be used normally by
-\fBssh\fR and \fBsshd\fR, but they do not reveal identifying information should
-the file's contents be disclosed. This option does not modify existing hashed
-host names and is therefore safe to use on files that mix hashed and non-hashed
-names.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-i\fR\fR
-.ad
-.RS 21n
-This option reads an unencrypted private (or public) key file in
-SSH2-compatible format and prints an OpenSSH compatible private (or public) key
-to stdout. \fBssh-keygen\fR also reads the "SECSH" Public Key File Format. This
-option allows importing keys from several other SSH implementations.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-l\fR\fR
-.ad
-.RS 21n
-Shows the fingerprint of the specified private or public key file.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-N\fR \fInew_passphrase\fR\fR
-.ad
-.RS 21n
-Provides the new passphrase.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-p\fR\fR
-.ad
-.RS 21n
-Requests changing the passphrase of a private key file instead of creating a
-new private key. The program prompts for the file containing the private key,
-for the old passphrase, and prompts twice for the new passphrase.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-P\fR \fIpassphrase\fR\fR
-.ad
-.RS 21n
-Provides the (old) passphrase.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-q\fR\fR
-.ad
-.RS 21n
-Silences \fBssh-keygen\fR.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-t\fR \fItype\fR\fR
-.ad
-.RS 21n
-Specifies the algorithm used for the key, where \fItype\fR is one of \fBrsa\fR,
-\fBdsa\fR, and \fBrsa1\fR. Type \fBrsa1\fR is used only for the SSHv1 protocol.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-R\fR \fIhostname\fR\fR
-.ad
-.RS 21n
-Removes all keys belonging to \fIhostname\fR from a \fBknown_hosts\fR file.
-This option is useful to delete hashed hosts. See \fB-H\fR.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-x\fR\fR
-.ad
-.RS 21n
-Obsolete. Replaced by the \fB-e\fR option.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-X\fR\fR
-.ad
-.RS 21n
-Obsolete. Replaced by the \fB-i\fR option.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-y\fR\fR
-.ad
-.RS 21n
-This option reads a private OpenSSH format file and prints an OpenSSH public
-key to stdout.
-.RE
-
-.SH EXIT STATUS
-.LP
-The following exit values are returned:
-.sp
-.ne 2
-.na
-\fB\fB0\fR\fR
-.ad
-.RS 5n
-Successful completion.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB1\fR\fR
-.ad
-.RS 5n
-An error occurred.
-.RE
-
-.SH FILES
-.ne 2
-.na
-\fB\fB$HOME/.ssh/identity\fR\fR
-.ad
-.RS 27n
-This file contains the RSA private key for the SSHv1 protocol. This file should
-not be readable by anyone but the user. It is possible to specify a passphrase
-when generating the key; that passphrase is used to encrypt the private part of
-this file using 3DES. This file is not automatically accessed by
-\fBssh-keygen\fR, but it is offered as the default file for the private key.
-\fBsshd\fR(1M) reads this file when a login attempt is made.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB$HOME/.ssh/identity.pub\fR\fR
-.ad
-.RS 27n
-This file contains the RSA public key for the SSHv1 protocol. The contents of
-this file should be added to \fB$HOME/.ssh/authorized_keys\fR on all machines
-where you wish to log in using \fBRSA\fR authentication. There is no need to
-keep the contents of this file secret.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB$HOME/.ssh/id_dsa\fR\fR
-.ad
-.br
-.na
-\fB\fB$HOME/.ssh/id_rsa\fR\fR
-.ad
-.RS 27n
-These files contain, respectively, the DSA or RSA private key for the SSHv2
-protocol. These files should not be readable by anyone but the user. It is
-possible to specify a passphrase when generating the key; that passphrase is
-used to encrypt the private part of the file using 3DES. Neither of these files
-is automatically accessed by \fBssh-keygen\fR but is offered as the default
-file for the private key. \fBsshd\fR(1M) reads this file when a login attempt
-is made.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB$HOME/.ssh/id_dsa.pub\fR\fR
-.ad
-.br
-.na
-\fB\fB$HOME/.ssh/id_rsa.pub\fR\fR
-.ad
-.RS 27n
-These files contain, respectively, the DSA or RSA public key for the SSHv2
-protocol. The contents of these files should be added, respectively, to
-\fB$HOME/.ssh/authorized_keys\fR on all machines where you wish to log in using
-DSA or RSA authentication. There is no need to keep the contents of these files
-secret.
-.RE
-
-.SH ATTRIBUTES
-.LP
-See \fBattributes\fR(5) for descriptions of the following attributes:
-.sp
-
-.sp
-.TS
-box;
-c | c
-l | l .
-ATTRIBUTE TYPE ATTRIBUTE VALUE
-_
-Interface Stability Committed
-.TE
-
-.SH SEE ALSO
-.LP
-\fBssh\fR(1), \fBssh-add\fR(1), \fBssh-agent\fR(1), \fBsshd\fR(1M),
-\fBattributes\fR(5)
diff --git a/usr/src/man/man1/ssh-keyscan.sunssh.1 b/usr/src/man/man1/ssh-keyscan.sunssh.1
deleted file mode 100644
index f4491fccc3..0000000000
--- a/usr/src/man/man1/ssh-keyscan.sunssh.1
+++ /dev/null
@@ -1,248 +0,0 @@
-'\" te
-.\" Copyright (c) 2004, Sun Microsystems, Inc. All Rights Reserved.
-.\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
-.\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
-.\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
-.TH SSH-KEYSCAN 1 "Jul 24, 2004"
-.SH NAME
-ssh-keyscan \- gather public ssh host keys of a number of hosts
-.SH SYNOPSIS
-.LP
-.nf
-\fBssh-keyscan\fR [\fB-v46\fR] [\fB-p\fR \fIport\fR] [\fB-T\fR \fItimeout\fR] [\fB-t\fR \fItype\fR]
- [\fB-f\fR \fIfile\fR] [\fB-\fR] [\fIhost\fR... | \fIaddrlist\fR \fInamelist\fR] [...]
-.fi
-
-.SH DESCRIPTION
-.LP
-\fBssh-keyscan\fR is a utility for gathering the public ssh host keys of a
-number of hosts. It was designed to aid in building and verifying
-\fBssh_known_hosts\fR files. \fBssh-keyscan\fR provides a minimal interface
-suitable for use by shell and perl scripts. The output of \fBssh-keyscan\fR is
-directed to standard output.
-.sp
-.LP
-\fBssh-keyscan\fR uses non-blocking socket I/O to contact as many hosts as
-possible in parallel, so it is very efficient. The keys from a domain of 1,000
-hosts can be collected in tens of seconds, even when some of those hosts are
-down or do not run ssh. For scanning, one does not need login access to the
-machines that are being scanned, nor does the scanning process involve any
-encryption.
-.SS "File Format"
-.LP
-Input format:
-.sp
-.in +2
-.nf
-1.2.3.4,1.2.4.4
-\fIname.my.domain,name,n.my.domain,n,\fR1.2.3.4,1.2.4.4
-.fi
-.in -2
-.sp
-
-.sp
-.LP
-Output format for \fBrsa1\fR keys:
-.sp
-.in +2
-.nf
-\fIhost-or-namelist bits exponent modulus\fR
-.fi
-.in -2
-.sp
-
-.sp
-.LP
-Output format for \fBrsa\fR and \fBdsa\fR keys, where \fIkeytype\fR is either
-\fBssh-rsa\fR or `\fBssh-dsa\fR:
-.sp
-.in +2
-.nf
-\fIhost-or-namelist keytype base64-encoded-key\fR
-.fi
-.in -2
-.sp
-
-.SH OPTIONS
-.LP
-The following options are supported:
-.sp
-.ne 2
-.na
-\fB\fB-f\fR \fIfilename\fR\fR
-.ad
-.RS 28n
-Read hosts or addrlist namelist pairs from this file, one per line. If you
-specity - instead of a filename, \fBssh-keyscan\fR reads hosts or addrlist
-namelist pairs from the standard input.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-p\fR \fIport\fR\fR
-.ad
-.RS 28n
-Port to connect to on the remote host.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-T\fR \fItimeout\fR\fR
-.ad
-.RS 28n
-Set the timeout for connection attempts. If \fItimeout\fR seconds have elapsed
-since a connection was initiated to a host or since the last time anything was
-read from that host, the connection is closed and the host in question is
-considered unavailable. The default is for \fItimeout\fR is 5 seconds.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-t\fR \fItype\fR\fR
-.ad
-.RS 28n
-Specify the type of the key to fetch from the scanned hosts. The possible
-values for \fItype\fR are \fBrsa1\fR for protocol version 1 and \fBrsa\fR or
-\fBdsa\fR for protocol version 2. Specify multiple values by separating them
-with commas. The default is \fBrsa1\fR.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-v\fR\fR
-.ad
-.RS 28n
-Specify verbose mode. Print debugging messages about progress.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-4\fR\fR
-.ad
-.RS 28n
-Force to use IPv4 addresses only.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-6\fR\fR
-.ad
-.RS 28n
-Forces to use IPv6 addresses only.
-.RE
-
-.SH SECURITY
-.LP
-If a \fBssh_known_hosts\fR file is constructed using \fBssh-keyscan\fR without
-verifying the keys, users are vulnerable to man-in-the-middle attacks. If the
-security model allows such a risk, \fBssh-keyscan\fR can help in the detection
-of tampered keyfiles or man-in-the-middle attacks which have begun after the
-\fBssh_known_hosts\fR file was created.
-.SH EXAMPLES
-.LP
-\fBExample 1 \fRPrinting the \fBrsa1\fR Host Key
-.sp
-.LP
-The following example prints the \fBrsa1\fR host key for machine
-\fBhostname\fR:
-
-.sp
-.in +2
-.nf
-$ ssh-keyscan hostname
-.fi
-.in -2
-.sp
-
-.LP
-\fBExample 2 \fRFinding All Hosts
-.sp
-.LP
-The following commands finds all hosts from the file \fBssh_hosts\fR which have
-new or different keys from those in the sorted file \fBssh_known_hosts\fR:
-
-.sp
-.in +2
-.nf
-$ ssh-keyscan -t rsa,dsa -f ssh_hosts | \e
- sort -u - ssh_known_hosts | diff ssh_known_hosts -
-.fi
-.in -2
-.sp
-
-.SH FILES
-.ne 2
-.na
-\fB\fB/etc/ssh_known_hosts\fR \fR
-.ad
-.RS 25n
-
-.RE
-
-.SH EXIT STATUS
-.LP
-The following exit values are returned:
-.sp
-.ne 2
-.na
-\fB\fB0\fR \fR
-.ad
-.RS 6n
-No usage errors. \fBssh-keyscan\fR might or might not have succeeded or failed
-to scan one, more or all of the given hosts.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB1\fR\fR
-.ad
-.RS 6n
-Usage error.
-.RE
-
-.SH ATTRIBUTES
-.LP
-See \fBattributes\fR(5) for descriptions of the following attributes:
-.sp
-
-.sp
-.TS
-box;
-c | c
-l | l .
-ATTRIBUTE TYPE ATTRIBUTE VALUE
-_
-Interface Stability Evolving
-.TE
-
-.SH SEE ALSO
-.LP
-\fBssh\fR(1), \fBsshd\fR(1M), \fBattributes\fR(5)
-.SH AUTHORS
-.LP
-David Mazieres wrote the initial version, and Wayne Davison added suppport for
-protocol version 2.
-.SH BUGS
-.LP
-\fBssh\(emkeyscan\fR generates
-.sp
-.in +2
-.nf
-Connection closed by remote host
-.fi
-.in -2
-.sp
-
-.sp
-.LP
-messages on the consoles of all machines it scans if the server is older than
-version 2.9. This is because \fBssh-keyscan\fR opens a connection to the
-\fBssh\fR port, reads the public key, and drops the connection as soon as it
-gets the key.
diff --git a/usr/src/man/man1/ssh-socks5-proxy-connect.sunssh.1 b/usr/src/man/man1/ssh-socks5-proxy-connect.sunssh.1
deleted file mode 100644
index 44903c0b9b..0000000000
--- a/usr/src/man/man1/ssh-socks5-proxy-connect.sunssh.1
+++ /dev/null
@@ -1,202 +0,0 @@
-'\" te
-.\" Copyright (c) 2002, Sun Microsystems, Inc. All Rights Reserved
-.\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
-.\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
-.\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
-.TH SSH-SOCKS5-PROXY-CONNECT 1 "Oct 30, 2002"
-.SH NAME
-ssh-socks5-proxy-connect \- Secure Shell proxy for SOCKS5
-.SH SYNOPSIS
-.LP
-.nf
-\fB/usr/lib/ssh/ssh-socks5-proxy-connect\fR
- [\fB-h\fR \fIsocks5_proxy_host\fR]
- [\fB-p\fR \fIsocks5_proxy_port\fR] \fIconnect_host\fR \fIconnect_port\fR
-.fi
-
-.SH DESCRIPTION
-.LP
-A proxy command for \fBssh\fR(1) that uses SOCKS5 (RFC 1928). Typical use is
-where connections external to a network are only allowed via a socks gateway
-server.
-.sp
-.LP
-This proxy command does not provide any of the SOCKS5 authentication mechanisms
-defined in RFC 1928. Only anonymous connections are possible.
-.SH OPTIONS
-.LP
-The following options are supported:
-.sp
-.ne 2
-.na
-\fB\fB-h\fR \fIsocks5_proxy_host\fR\fR
-.ad
-.RS 24n
-Specifies the proxy web server through which to connect. Overrides the
-\fBSOCKS5_SERVER\fR environment variable.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-p\fR \fIsocks5_proxy_port\fR\fR
-.ad
-.RS 24n
-Specifies the port on which the proxy web server runs. If not specified, port
-80 is assumed. Overrides the \fBSOCKS5_PORT\fR environment variable.
-.RE
-
-.SH OPERANDS
-.LP
-The following operands are supported:
-.sp
-.ne 2
-.na
-\fB\fIsocks5_proxy_host\fR\fR
-.ad
-.RS 21n
-The host name or IP address (IPv4 or IPv6) of the proxy.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fIsocks5_proxy_port\fR\fR
-.ad
-.RS 21n
-The numeric port number to connect to on \fIsocks5_proxy_host\fR.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fIconnect_host\fR\fR
-.ad
-.RS 21n
-The name of the remote host to which the socks gateway is to connect you.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fIconnect_port\fR\fR
-.ad
-.RS 21n
-The numeric port number of the socks gateway to connect you to on
-\fIconnect_host\fR.
-.RE
-
-.SH EXAMPLES
-.LP
-The recommended way to use a proxy connection command is to configure the
-\fBProxyCommand\fR in \fBssh_config\fR(4) (see Example 1 and Example 2).
-Example 3 shows how the proxy command can be specified on the command line when
-running \fBssh\fR(1).
-.LP
-\fBExample 1 \fRSetting the proxy from the environment
-.sp
-.LP
-The following example uses \fBssh-socks5-proxy-connect\fR in
-\fBssh_config\fR(4) when the proxy is set from the environment:
-
-.sp
-.in +2
-.nf
-\fBHost playtime.foo.com
- ProxyCommand /usr/lib/ssh/ssh-socks5-proxy-connect \e
- playtime.foo.com 22\fR
-.fi
-.in -2
-.sp
-
-.LP
-\fBExample 2 \fROverriding proxy environment variables
-.sp
-.LP
-The following example uses \fBssh-socks5-proxy-connect\fR in
-\fBssh_config\fR(4) to override (or if not set) proxy environment variables:
-
-.sp
-.in +2
-.nf
-\fBHost playtime.foo.com
- ProxyCommand /usr/lib/ssh/ssh-socks5-proxy-connect -h socks-gw \e
- -p 1080 playtime.foo.com 22\fR
-.fi
-.in -2
-.sp
-
-.LP
-\fBExample 3 \fRUsing the command line
-.sp
-.LP
-The following example uses \fBssh-socks5-proxy-connect\fR from the \fBssh\fR(1)
-command line:
-
-.sp
-.in +2
-.nf
-example$ \fBssh -o'ProxyCommand=/usr/lib/ssh/ssh-socks5-proxy-connect \e
- -h socks-gw -p 1080 playtime.foo.com 22' playtime.foo.com\fR
-.fi
-.in -2
-.sp
-
-.SH ENVIRONMENT VARIABLES
-.ne 2
-.na
-\fB\fBSOCKS5_SERVER\fR\fR
-.ad
-.RS 17n
-Takes \fIsocks5_proxy_host\fR operand to specify the default proxy host.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fBSOCKS5_PORT\fR\fR
-.ad
-.RS 17n
-Takes \fIsocks5_proxy_port \fR operand to specify the default proxy port.
-.RE
-
-.SH EXIT STATUS
-.LP
-The following exit values are returned:
-.sp
-.ne 2
-.na
-\fB\fB0\fR \fR
-.ad
-.RS 6n
-Successful completion.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB1\fR \fR
-.ad
-.RS 6n
-An error occurred.
-.RE
-
-.SH ATTRIBUTES
-.LP
-See \fBattributes\fR(5) for descriptions of the following attributes:
-.sp
-
-.sp
-.TS
-box;
-c | c
-l | l .
-ATTRIBUTE TYPE ATTRIBUTE VALUE
-_
-Interface Stability Stable
-.TE
-
-.SH SEE ALSO
-.LP
-\fBssh\fR(1), \fBssh-http-proxy-connect\fR(1), \fBssh_config\fR(4),
-\fBattributes\fR(5)
diff --git a/usr/src/man/man1/ssh.sunssh.1 b/usr/src/man/man1/ssh.sunssh.1
deleted file mode 100644
index 88d8c56fdc..0000000000
--- a/usr/src/man/man1/ssh.sunssh.1
+++ /dev/null
@@ -1,979 +0,0 @@
-'\" te
-.\" To view license terms, attribution, and copyright for OpenSSH, the default path is /var/sadm/pkg/SUNWsshdr/install/copyright. If the Solaris operating environment has been installed anywhere other than the default, modify the specified path to access the file at
-.\" the installed location.
-.\" Portions Copyright (c) 2009, Sun Microsystems, Inc. All Rights Reserved.
-.TH SSH 1 "May 20, 2009"
-.SH NAME
-ssh \- secure shell client (remote login program)
-.SH SYNOPSIS
-.LP
-.nf
-\fBssh\fR [\fB-l\fR \fIlogin_name\fR] \fIhostname\fR | \fIuser@hostname\fR [ \fIcommand\fR]
-.fi
-
-.LP
-.nf
-\fBssh\fR [\fB-afgknqstvxACNTX1246\fR] [\fB-b\fR \fIbind_address\fR] [\fB-m\fR \fImac_spec\fR]
- [\fB-c\fR \fIcipher_spec\fR] [\fB-e\fR \fIescape_char\fR] [\fB-i\fR \fIidentity_file\fR]
- [\fB-l\fR \fIlogin_name\fR] [\fB-F\fR \fIconfigfile\fR] [\fB-o\fR \fIoption\fR] [\fB-p\fR \fIport\fR]
- [\fB-L\fR [\fIbind_address\fR\fB:\fR]\fIport\fR\fB:\fR\fIhost\fR\fB:\fR\fIhostport\fR]
- [\fB-R\fR [\fIbind_address\fR\fB:\fR]\fIport\fR\fB:\fR\fIhost\fR\fB:\fR\fIhostport\fR]
- [\fB-D\fR [\fIbind_address\fR\fB:\fR]\fIport\fR] \fIhostname\fR | \fIuser\fR\fB@\fR\fIhostname\fR [\fIcommand\fR]
-.fi
-
-.SH DESCRIPTION
-.LP
-\fBssh\fR (Secure Shell) is a program for logging into a remote machine and for
-executing commands on a remote machine. It is intended to replace \fBrlogin\fR
-and \fBrsh\fR, and to provide secure encrypted communications between two
-untrusted hosts over an insecure network. X11 connections and arbitrary TCP/IP
-ports can also be forwarded over the secure channel.
-.sp
-.LP
-\fBssh\fR connects and logs into the specified hostname. The user must prove
-his or her identity to the remote machine using one of several methods
-depending on the protocol version used:
-.SS "SSH Protocol Version 1"
-.LP
-First, if the machine the user logs in from is listed in \fB/etc/hosts.equiv\fR
-or \fB/etc/shosts.equiv\fR on the remote machine, and the user names are the
-same on both sides, the user is immediately permitted to log in. Second,
-if .\fBrhosts\fR or \fB\&.shosts\fR exists in the user's home directory on the
-remote machine and contains a line containing the name of the client machine
-and the name of the user on that machine, the user is permitted to log in. This
-form of authentication alone is normally not allowed by the server because it
-is not secure.
-.sp
-.LP
-The second (and primary) authentication method is the \fBrhosts\fR or
-\fBhosts.equiv\fR method combined with RSA-based host authentication. It means
-that if the login would be permitted by \fB$HOME/.rhosts\fR,
-\fB$HOME/.shosts\fR, \fB/etc/hosts.equiv\fR, or \fB/etc/shosts.equiv\fR, and if
-additionally the server can verify the client's host key (see
-\fB/etc/ssh_known_hosts\fR in the FILES section), only then is login permitted.
-This authentication method closes security holes due to \fBIP\fR spoofing,
-\fBDNS\fR spoofing, and routing spoofing.
-.sp
-.LP
-\fBNote to the administrator:\fR \fB/etc/hosts.equiv\fR, \fB$HOME/.rhosts\fR,
-and the rlogin/rsh protocol in general, are inherently insecure and should be
-disabled if security is desired.
-.sp
-.LP
-As a third authentication method, \fBssh\fR supports \fBRSA\fR-based
-authentication. The scheme is based on public-key cryptography. There are
-cryptosystems where encryption and decryption are done using separate keys, and
-it is not possible to derive the decryption key from the encryption key.
-\fBRSA\fR is one such system. The idea is that each user creates a
-public/private key pair for authentication purposes. The server knows the
-public key, and only the user knows the private key. The file
-\fB$HOME/.ssh/authorized_keys\fR lists the public keys that are permitted for
-logging in. When the user logs in, the \fBssh\fR program tells the server which
-key pair it would like to use for authentication. The server checks if this key
-is permitted, and if so, sends the user (actually the \fBssh\fR program running
-on behalf of the user) a challenge in the form of a random number, encrypted by
-the user's public key. The challenge can only be decrypted using the proper
-private key. The user's client then decrypts the challenge using the private
-key, proving that he or she knows the private key but without disclosing it to
-the server.
-.sp
-.LP
-\fBssh\fR implements the \fBRSA\fR authentication protocol automatically. The
-user creates his or her \fBRSA\fR key pair by running \fBssh-keygen\fR(1). This
-stores the private key in \fB$HOME/.ssh/identity\fR and the public key in
-\fB$HOME/.ssh/identity.pub\fR in the user's home directory. The user should
-then copy the \fBidentity.pub\fR to \fB$HOME/.ssh/authorized_keys\fR in his or
-her home directory on the remote machine (the \fBauthorized_keys\fR file
-corresponds to the conventional \fB$HOME/.rhosts\fR file, and has one key per
-line, though the lines can be very long). After this, the user can log in
-without giving the password. \fBRSA\fR authentication is much more secure than
-\fBrhosts\fR authentication.
-.sp
-.LP
-The most convenient way to use \fBRSA\fR authentication can be with an
-authentication agent. See \fBssh-agent\fR(1) for more information.
-.sp
-.LP
-If other authentication methods fail, \fBssh\fR prompts the user for a
-password. The password is sent to the remote host for checking. However, since
-all communications are encrypted, the password cannot be seen by someone
-listening on the network.
-.SS "SSH Protocol Version 2"
-.LP
-The SSH version 2 protocol supports multiple user authentication methods, some
-of which are similar to those available with the SSH protocol version 1. These
-authentication mechanisms are negotiated by the client and server, with the
-client trying methods in the order specified in the
-\fBPreferredAuthentications\fR client configuration option. The server decides
-when enough authentication methods have passed successfully so as to complete
-the authentication phase of the protocol.
-.sp
-.LP
-When a user connects by using protocol version 2, similar authentication
-methods are available. Using the default values for
-\fBPreferredAuthentications\fR, the client tries to authenticate first by using
-the hostbased method. If this method fails, public key authentication is
-attempted. Finally, if this method fails, keyboard-interactive and password
-authentication are tried.
-.sp
-.LP
-The public key method is similar to \fBRSA\fR authentication described in the
-previous section and allows the \fBRSA\fR or \fBDSA\fR algorithm to be used:
-The client uses his or her private key, \fB$HOME/.ssh/id_dsa\fR or
-\fB$HOME/.ssh/id_rsa\fR, to sign the session identifier and sends the result to
-the server. The server checks whether the matching public key is listed in
-\fB$HOME/.ssh/authorized_keys\fR and grants access if both the key is found and
-the signature is correct. The session identifier is derived from a shared
-Diffie-Hellman value and is only known to the client and the server.
-.sp
-.LP
-If public key authentication fails or is not available, a password can be sent
-encrypted to the remote host for proving the user's identity, or an extended
-prompt/reply protocol can be engaged.
-.sp
-.LP
-Additionally, \fBssh\fR supports hostbased or challenge response
-authentication.
-.sp
-.LP
-Protocol 2 provides additional mechanisms for confidentiality (the traffic is
-encrypted using 3DES, Blowfish, CAST128 or Arcfour) and integrity
-(\fBhmac-sha1\fR, \fBhmac-md5\fR). Protocol 1 lacks a strong mechanism for
-ensuring the integrity of the connection.
-.SS "Login Session and Remote Execution"
-.LP
-When the user's identity has been accepted by the server, the server either
-executes the specified command, or logs into the machine and gives the user a
-normal shell on the remote machine. All communication with the remote command
-or shell is automatically encrypted.
-.sp
-.LP
-If a pseudo-terminal has been allocated (normal login session), the user can
-use the escape characters noted below. If a pseudo-terminal has been allocated
-(normal login session), the user can disconnect with \fB~.\fR, and suspend
-\fBssh\fR with \fB~^Z\fR. All forwarded connections can be listed with
-\fB~#\fR. If the session blocks waiting for forwarded X11 or TCP/IP connections
-to terminate, \fBssh\fR can be backgrounded with \fB~&\fR, although this should
-not be used while the user shell is active, as it can cause the shell to hang.
-All available escapes can be listed with \fB~?\fR.
-.sp
-.LP
-A single tilde character can be sent as \fB~~\fR, or by following the tilde
-with a character other than those described above. The escape character must
-always follow a newline to be interpreted as special. The escape character can
-be changed in configuration files or on the command line.
-.sp
-.LP
-If no pseudo tty has been allocated, the session is transparent and can be used
-to reliably transfer binary data. On most systems, setting the escape character
-to "\fBnone\fR" also makes the session transparent even if a tty is used.
-.sp
-.LP
-The session terminates when the command or shell on the remote machine exits
-and all X11 and TCP/IP connections have been closed. The exit status of the
-remote program is returned as the exit status of \fBssh\fR.
-.SS "Escape Characters"
-.LP
-When a pseudo-terminal has been requested, \fBssh\fR supports a number of
-functions through the use of an escape character.
-.sp
-.LP
-A single tilde character can be sent as \fB~~\fR or by following the tilde with
-a character other than those described below. The escape character must always
-follow a newline to be interpreted as special. The escape character can be
-changed in configuration files using the \fBEscapeChar\fR configuration
-directive or on the command line by the \fB-e\fR option.
-.sp
-.LP
-The supported escapes, assuming the default \fB~\fR, are:
-.sp
-.ne 2
-.na
-\fB\fB~.\fR\fR
-.ad
-.RS 7n
-Disconnect.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB~^Z\fR\fR
-.ad
-.RS 7n
-Background \fBssh\fR.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB~#\fR\fR
-.ad
-.RS 7n
-List forwarded connections.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB~&\fR\fR
-.ad
-.RS 7n
-Background \fBssh\fR at logout when waiting for forwarded connection / X11
-sessions to terminate.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB~?\fR\fR
-.ad
-.RS 7n
-Display a list of escape characters.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB~B\fR\fR
-.ad
-.RS 7n
-Send a break to the remote system. Only useful for SSH protocol version 2 and
-if the peer supports it.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB~C\fR\fR
-.ad
-.RS 7n
-Open command line. Only useful for adding port forwardings using the \fB-L\fR
-and \fB-R\fR options).
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB~R\fR\fR
-.ad
-.RS 7n
-Request rekeying of the connection. Only useful for SSH protocol version 2 and
-if the peer supports it.
-.RE
-
-.SS "X11 and TCP Forwarding"
-.LP
-If the \fBForwardX11\fR variable is set to ``\fByes\fR'' (or, see the
-description of the \fB-X\fR and \fB-x\fR options described later) and the user
-is using X11 (the \fBDISPLAY\fR environment variable is set), the connection to
-the X11 display is automatically forwarded to the remote side in such a way
-that any X11 programs started from the shell (or command) goes through the
-encrypted channel, and the connection to the real X server is made from the
-local machine. The user should not manually set \fBDISPLAY\fR. Forwarding of
-X11 connections can be configured on the command line or in configuration
-files.
-.sp
-.LP
-The \fBDISPLAY\fR value set by \fBssh\fR points to the server machine, but with
-a display number greater than zero. This is normal behavior, because \fBssh\fR
-creates a "proxy" X11 server on the server machine for forwarding the
-connections over the encrypted channel.
-.sp
-.LP
-\fBssh\fR also automatically sets up \fBXauthority\fR data on the server
-machine. For this purpose, it generates a random authorization cookie, store it
-in \fBXauthority\fR on the server, and verify that any forwarded connections
-carry this cookie and replace it by the real cookie when the connection is
-opened. The real authentication cookie is never sent to the server machine (and
-no cookies are sent in the plain).
-.sp
-.LP
-If the \fBForwardAgent\fR variable is set to "\fByes\fR" (or, see the
-description of the \fB-A\fR and \fB-a\fR options described later) and the user
-is using an authentication agent, the connection to the agent is automatically
-forwarded to the remote side.
-.sp
-.LP
-Forwarding of arbitrary TCP/IP connections over the secure channel can be
-specified either on the command line or in a configuration file. One possible
-application of TCP/IP forwarding is a secure connection to an electronic purse.
-Another possible application is firewall traversal.
-.SS "Server Authentication"
-.LP
-\fBssh\fR automatically maintains and checks a database containing
-identifications for all hosts it has ever been used with. Host keys are stored
-in \fB$HOME/.ssh/known_hosts\fR in the user's home directory. Additionally, the
-file \fB/etc/ssh_known_hosts\fR is automatically checked for known hosts. The
-behavior of \fBssh\fR with respect to unknown host keys is controlled by the
-\fBStrictHostKeyChecking\fR parameter. If a host's identification ever changes,
-\fBssh\fR warns about this and disables password authentication to prevent a
-trojan horse from getting the user's password. Another purpose of this
-mechanism is to prevent attacks by intermediaries which could otherwise be used
-to circumvent the encryption. The \fBStrictHostKeyChecking\fR option can be
-used to prevent logins to machines whose host key is not known or has changed.
-.sp
-.LP
-However, when using key exchange protected by GSS-API, the server can advertise
-a host key. The client automatically adds this host key to its known hosts
-file, \fB$HOME/.ssh/known_hosts\fR, regardless of the setting of the
-\fBStrictHostKeyChecking\fR option, unless the advertised host key collides
-with an existing known hosts entry.
-.sp
-.LP
-When the user's GSS-API credentials expire, the client continues to be able to
-rekey the session using the server's public host key to protect the key
-exchanges.
-.SS "GSS-API User and Server Authentication"
-.LP
-\fBssh\fR uses the user's GSS-API credentials to authenticate the client to the
-server wherever possible, if \fBGssKeyEx\fR and/or \fBGssAuthentication\fR are
-set.
-.sp
-.LP
-With \fBGssKeyEx\fR, one can have an SSHv2 server that has no host public keys,
-so that only \fBGssKeyEx\fR can be used. With such servers, rekeying fails if
-the client's credentials are expired.
-.sp
-.LP
-GSS-API user authentication has the disadvantage that it does not obviate the
-need for SSH host keys, but its failure does not impact rekeying. \fBssh\fR can
-try other authentication methods (such as public key, password, and so on) if
-GSS-API authentication fails.
-.sp
-.LP
-Delegation of GSS-API credentials can be quite useful, but is not without
-danger. As with passwords, users should not delegate GSS credentials to
-untrusted servers, since a compromised server can use a user's delegated GSS
-credentials to impersonate the user.
-.sp
-.LP
-GSS-API user authorization is covered in \fBgss_auth_rules\fR(5).
-.sp
-.LP
-Rekeying can be used to redelegate credentials when \fBGssKeyEx\fR is
-"\fByes\fR". (See \fB~R\fR under \fBEscape Characters\fR above.)
-.SH OPTIONS
-.LP
-The following options are supported:
-.sp
-.ne 2
-.na
-\fB\fB-1\fR\fR
-.ad
-.sp .6
-.RS 4n
-Forces \fBssh\fR to try protocol version 1 only.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-2\fR\fR
-.ad
-.sp .6
-.RS 4n
-Forces \fBssh\fR to try protocol version 2 only.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-4\fR\fR
-.ad
-.sp .6
-.RS 4n
-Forces \fBssh\fR to use IPv4 addresses only.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-6\fR\fR
-.ad
-.sp .6
-.RS 4n
-Forces \fBssh\fR to use IPv6 addresses only.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-a\fR\fR
-.ad
-.sp .6
-.RS 4n
-Disables forwarding of the authentication agent connection.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-A\fR\fR
-.ad
-.sp .6
-.RS 4n
-Enables forwarding of the authentication agent connection. This can also be
-specified on a per-host basis in a configuration file.
-.sp
-Agent forwarding should be enabled with caution. Users with the ability to
-bypass file permissions on the remote host (for the agent's UNIX-domain socket)
-can access the local agent through the forwarded connection. An attacker cannot
-obtain key material from the agent. However, the attacker can perform
-operations on the keys that enable the attacker to authenticate using the
-identities loaded into the agent.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-b\fR \fIbind_address\fR\fR
-.ad
-.sp .6
-.RS 4n
-Specifies the interface to transmit from on machines with multiple interfaces
-or aliased addresses.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-c\fR \fIcipher_spec\fR\fR
-.ad
-.sp .6
-.RS 4n
-Selects the cipher specification for encrypting the session.
-.sp
-For protocol version 1, \fIcipher_spec\fR is a single cipher. See the
-\fBCipher\fR option in \fBssh_config\fR(4) for more information.
-.sp
-For protocol version 2, \fIcipher_spec\fR is a comma-separated list of ciphers
-listed in order of preference. See the \fICiphers\fR option in
-\fBssh_config\fR(4) for more information.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-C\fR\fR
-.ad
-.sp .6
-.RS 4n
-Requests compression of all data (including stdin, stdout, stderr, and data for
-forwarded X11 and TCP/IP connections). The compression algorithm is the same
-used by \fBgzip\fR(1). The \fBgzip\fR man page is available in the
-\fBSUNWsfman\fR package. The "level" can be controlled by the
-\fBCompressionLevel\fR option (see \fBssh_config\fR(4)). Compression is
-desirable on modem lines and other slow connections, but only slows down things
-on fast networks. The default value can be set on a host-by-host basis in the
-configuration files. See the \fBCompression\fR option in \fBssh_config\fR(4).
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-D\fR [\fIbind_address\fR\fB:\fR]\fIport\fR\fR
-.ad
-.sp .6
-.RS 4n
-Specifies a local \fBdynamic\fR application-level port forwarding. This works
-by allocating a socket to listen to port on the local side, optionally bound to
-the specified \fIbind_address\fR. Whenever a connection is made to this port,
-the connection is forwarded over the secure channel. The application protocol
-is then used to determine where to connect to from the remote machine.
-Currently, the \fBSOCKS4\fR and \fBSOCKS5\fR protocols are supported and
-\fBssh\fR acts as a SOCKS server. Only a user with enough privileges can
-forward privileged ports. Dynamic port forwardings can also be specified in the
-configuration file.
-.sp
-IPv6 addresses can be specified with an alternative syntax:
-\fB[\fR\fIbind_address\fR\fB/]\fR\fIport\fR or by enclosing the address in
-square brackets. By default, the local port is bound in accordance with the
-\fBGatewayPorts\fR setting. However, an explicit \fIbind_address\fR can be used
-to bind the connection to a specific address. The \fIbind_address\fR of
-\fBlocalhost\fR indicates that the listening port be bound for local use only,
-while an empty address or \fB*\fR indicates that the port should be available
-from all interfaces.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-e\fR \fIch\fR | ^\fIch\fR | none\fR
-.ad
-.sp .6
-.RS 4n
-Sets the escape character for sessions with a pty (default: `\fB~\fR'). The
-escape character is only recognized at the beginning of a line. The escape
-character followed by a dot (\fB\&.\fR) closes the connection. If followed by
-CTRL-z, the escape character suspends the connection. If followed by itself,
-the escape character sends itself once. Setting the character to \fBnone\fR
-disables any escapes and makes the session fully transparent.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-f\fR\fR
-.ad
-.sp .6
-.RS 4n
-Requests \fBssh\fR to go to background just before command execution. This is
-useful if \fBssh\fR is going to ask for passwords or passphrases, but the user
-wants it in the background. This implies the \fB-n\fR option. The recommended
-way to start X11 programs at a remote site is with something like \fBssh\fR
-\fB-f\fR \fIhost\fR \fIxterm\fR.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-F\fR \fIconfigfile\fR\fR
-.ad
-.sp .6
-.RS 4n
-Specifies an alternative per-user configuration file. If a configuration file
-is specified on the command line, the system-wide configuration file,
-\fB/etc/ssh_config\fR, is ignored. The default for the per-user configuration
-file is \fB$HOME/.ssh/config\fR.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-g\fR\fR
-.ad
-.sp .6
-.RS 4n
-Allows remote hosts to connect to local forwarded ports.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-i\fR \fIidentity_file\fR\fR
-.ad
-.sp .6
-.RS 4n
-Selects a file from which the identity (private key) for \fBRSA\fR or \fBDSA\fR
-authentication is read. The default is \fB$HOME/.ssh/identity\fR for protocol
-version 1, and \fB$HOME/.ssh/id_rsa\fR and \fB$HOME/.ssh/id_dsa\fR for protocol
-version 2. Identity files can also be specified on a per-host basis in the
-configuration file. It is possible to have multiple \fB-i\fR options (and
-multiple identities specified in configuration files).
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-l\fR \fIlogin_name\fR\fR
-.ad
-.sp .6
-.RS 4n
-Specifies the user to log in as on the remote machine. This also can be
-specified on a per-host basis in the configuration file.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-L\fR [\fIbind_address:\fR]\fIport\fR:\fIhost\fR:\fIhostport\fR\fR
-.ad
-.sp .6
-.RS 4n
-Specifies that the specified port on the local (client) host is to be forwarded
-to the specified host and port on the remote side. This works by allocating a
-socket to listen to the port on the local side, optionally bound to the
-specified \fIbind_address\fR. Then, whenever a connection is made to this port,
-the connection is forwarded over the secure channel and a connection is made to
-host port \fIhostport\fR from the remote machine. Port forwardings can also be
-specified in the configuration file. Only a user with enough privileges can
-forward privileged ports. IPv6 addresses can be specified with an alternative
-syntax: \fB[\fR\fIbind_address\fR\fB/]\fR\fIport\fR\fB/\fR\fIhost\fR\fB/\fR\fIh
-ostport\fR or by enclosing the address in square brackets.
-.sp
-By default, the local port is bound in accordance with the \fBGatewayPorts\fR
-setting. However, an explicit \fIbind_address\fR can be used to bind the
-connection to a specific address. The \fIbind_address\fR of \fBlocalhost\fR
-indicates that the listening port be bound for local use only, while an empty
-address or \fB*\fR indicates that the port should be available from all
-interfaces.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-m\fR \fImac_spec\fR\fR
-.ad
-.sp .6
-.RS 4n
-Additionally, for protocol version 2 a comma-separated list of \fBMAC\fR
-(message authentication code) algorithms can be specified in order of
-preference. See the MACs keyword for more information.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-n\fR\fR
-.ad
-.sp .6
-.RS 4n
-Redirects \fBstdin\fR from \fB/dev/null\fR (actually, prevents reading from
-\fBstdin\fR). This must be used when \fBssh\fR is run in the background. A
-common trick is to use this to run X11 programs on a remote machine. For
-example,
-.sp
-.in +2
-.nf
-ssh -n shadows.cs.hut.fi emacs &
-.fi
-.in -2
-.sp
-
-starts an \fBemacs\fR on \fBshadows.cs.hut.fi\fR, and the X11 connection is
-automatically forwarded over an encrypted channel. The \fBssh\fR program is put
-in the background. This does not work if \fBssh\fR needs to ask for a password
-or passphrase. See also the \fB-f\fR option.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-N\fR\fR
-.ad
-.sp .6
-.RS 4n
-Does not execute a remote command. This is useful if you just want to forward
-ports (protocol version 2 only).
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-o\fR \fIoption\fR\fR
-.ad
-.sp .6
-.RS 4n
-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 command-line
-flag. The option has the same format as a line in the configuration file.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-p\fR \fIport\fR\fR
-.ad
-.sp .6
-.RS 4n
-Specifies the port to connect to on the remote host. This can be specified on a
-per-host basis in the configuration file.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-P\fR\fR
-.ad
-.sp .6
-.RS 4n
-Obsoleted option. SSHv1 connections from privileged ports are not supported.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-q\fR\fR
-.ad
-.sp .6
-.RS 4n
-Quiet mode. Causes all warning and diagnostic messages to be suppressed. Only
-fatal errors are displayed.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-R\fR [\fIbind_address\fR:]\fIport\fR:\fIhost\fR:\fIhostport\fR\fR
-.ad
-.sp .6
-.RS 4n
-Specifies that the specified port on the remote (server) host is to be
-forwarded to the specified host and port on the local side. This works by
-allocating a socket to listen to the port on the remote side. Then, whenever a
-connection is made to this port, the connection is forwarded over the secure
-channel and a connection is made to host port \fIhostport\fR from the local
-machine. Port forwardings can also be specified in the configuration file.
-Privileged ports can be forwarded only when logging in on the remote machine as
-a user with enough privileges.
-.sp
-IPv6 addresses can be specified by enclosing the address in square braces or
-using an alternative syntax: \fB[\fR\fIbind_address\fR\fB/]\fR\fIhost\fR\fB/\fR
-\fIport\fR\fB/\fR\fIhostport\fR.
-.sp
-By default, the listening socket on the server is bound to the loopback
-interface only. This can be overridden by specifying a \fIbind_address\fR. An
-empty \fIbind_address\fR, or the address \fB*\fR, indicates that the remote
-socket should listen on all interfaces. Specifying a remote \fIbind_address\fR
-only succeeds if the server's \fBGatewayPorts\fR option is enabled. See
-\fBsshd_config\fR(4).
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-s\fR\fR
-.ad
-.sp .6
-.RS 4n
-Can be used to request invocation of a subsystem on the remote system.
-Subsystems are a feature of the SSH2 protocol which facilitate the use of SSH
-as a secure transport for other applications, for example, \fBsftp\fR. The
-subsystem is specified as the remote command.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-t\fR\fR
-.ad
-.sp .6
-.RS 4n
-Forces pseudo-tty allocation. This can be used to execute arbitrary
-screen-based programs on a remote machine, which can be very useful, for
-example, when implementing menu services. Multiple \fB-t\fR options force
-allocation, even if \fBssh\fR has no local \fBtty\fR.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-T\fR\fR
-.ad
-.sp .6
-.RS 4n
-Disables pseudo-tty allocation (protocol version 2 only).
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-v\fR\fR
-.ad
-.sp .6
-.RS 4n
-Verbose mode. Causes \fBssh\fR to print debugging messages about its progress.
-This is helpful in debugging connection, authentication, and configuration
-problems. Multiple \fB-v\fR options increase the verbosity. Maximum is 3.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-x\fR\fR
-.ad
-.sp .6
-.RS 4n
-Disables X11 forwarding.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB-X\fR\fR
-.ad
-.sp .6
-.RS 4n
-Enables X11 forwarding. This can also be specified on a per-host basis in a
-configuration file.
-.sp
-X11 forwarding should be enabled with caution. Users with the ability to bypass
-file permissions on the remote host (for the user's X authorization database)
-can access the local X11 display through the forwarded connection. An attacker
-can then be able to perform activities such as keystroke monitoring.
-.sp
-For this reason, X11 forwarding might be subjected to X11 SECURITY extension
-restrictions. Refer to the \fBForwardX11Trusted\fR directive in
-\fBssh_config\fR(4) for more information.
-.sp
-If X11 forwarding is enabled, remote X11 clients is trusted by default. This
-means that they have full access to the original X11 display.
-.RE
-
-.SH ENVIRONMENT VARIABLES
-.LP
-\fBssh\fR normally sets the following environment variables:
-.sp
-.ne 2
-.na
-\fB\fBDISPLAY\fR\fR
-.ad
-.sp .6
-.RS 4n
-The \fBDISPLAY\fR variable must be set for X11 display forwarding to work.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fBSSH_ASKPASS\fR\fR
-.ad
-.sp .6
-.RS 4n
-If \fBssh\fR needs a passphrase, it reads the passphrase from the current
-terminal if it was run from a terminal. If \fBssh\fR does not have a terminal
-associated with it but \fBDISPLAY\fR and \fBSSH_ASKPASS\fR are set, it executes
-the program specified by \fBSSH_ASKPASS\fR and opens an X11 window to read the
-passphrase. This is particularly useful when calling \fBssh\fR from a .Xsession
-or related script. On some machines it might be necessary to redirect the input
-from \fB/dev/null\fR to make this work. The system is shipped with
-\fB/usr/lib/ssh/ssh-askpass\fR which is the default value for \fBSSH_ASKPASS\fR
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fBSSH_AUTH_SOCK\fR\fR
-.ad
-.sp .6
-.RS 4n
-Indicates the path of a unix-domain socket used to communicate with the agent.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fBSSH_LANGS\fR\fR
-.ad
-.sp .6
-.RS 4n
-A comma-separated list of IETF language tags (see RFC3066) indicating the
-languages that the user can read and write. Used for negotiation of the locale
-on the server.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fBLANG\fR, \fBLC_ALL\fR, \fBLC_COLLATE\fR, \fBLC_CTYPE\fR,\fR
-.ad
-.br
-.na
-\fB\fBLC_MESSAGES\fR, \fBLC_MONETARY\fR, \fBLC_NUMERIC\fR, \fBLC_TIME\fR\fR
-.ad
-.sp .6
-.RS 4n
-The values of these environment variables can be set in remote sessions
-according to the locale settings on the client side and availability of support
-for those locales on the server side. Environment Variable Passing (see \fIRFC
-4254\fR) is used for passing them over to the server side.
-.RE
-
-.sp
-.LP
-See the \fBENVIRONMENT VARIABLES\fR section in the \fBsshd\fR(1M) man page for
-more information on how locale setting can be further changed depending on
-server side configuration.
-.SH EXIT STATUS
-.LP
-The status of the remote program is returned as the exit status of \fBssh\fR.
-\fB255\fR is returned if an error occurred at anytime during the \fBssh\fR
-connection, including the initial key exchange.
-.SH FILES
-.ne 2
-.na
-\fB\fB$HOME/.ssh/known_hosts\fR\fR
-.ad
-.RS 26n
-Records host keys for all hosts the user has logged into that are not in
-\fB/etc/ssh/ssh_known_hosts\fR. See \fBsshd\fR(1M).
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB$HOME/.ssh/identity\fR\fR
-.ad
-.br
-.na
-\fB\fB$HOME/.ssh/id_dsa\fR\fR
-.ad
-.br
-.na
-\fB\fB$HOME/.ssh/id_ssa\fR\fR
-.ad
-.RS 26n
-Contains the authentication identity of the user. These files are for protocol
-1 \fBRSA\fR, protocol 2 \fBDSA\fR, and protocol 2 \fBRSA\fR, respectively.
-These files contain sensitive data and should be readable by the user but not
-accessible by others (read/write/execute). \fBssh\fR ignores a private key file
-if it is accessible by others. It is possible to specify a passphrase when
-generating the key. The passphrase is used to encrypt the sensitive part of
-this file using \fB3DES\fR.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB/etc/ssh/sshrc\fR\fR
-.ad
-.RS 26n
-Commands in this file are executed by \fBssh\fR when the user logs in just
-before the user's shell or command is started. See \fBsshd\fR(1M) for more
-information.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB$HOME/.ssh/rc\fR\fR
-.ad
-.RS 26n
-Commands in this file are executed by \fBssh\fR when the user logs in just
-before the user's shell or command is started. See \fBsshd\fR(1M) for more
-information.
-.RE
-
-.sp
-.ne 2
-.na
-\fB\fB$HOME/.ssh/environment\fR\fR
-.ad
-.RS 26n
-Contains additional definitions for environment variables. See ENVIRONMENT
-VARIABLES.
-.RE
-
-.SH ATTRIBUTES
-.LP
-See \fBattributes\fR(5) for descriptions of the following attributes:
-.sp
-
-.sp
-.TS
-box;
-c | c
-l | l .
-ATTRIBUTE TYPE ATTRIBUTE VALUE
-_
-Interface Stability See below.
-.TE
-
-.sp
-.LP
-The command line syntax is Committed. The remote locale selection through
-passing \fBLC_*\fR environment variables is Uncommitted.
-.SH SEE ALSO
-.LP
-\fBrlogin\fR(1), \fBrsh\fR(1), \fBscp\fR(1), \fBssh-add\fR(1),
-\fBssh-agent\fR(1), \fBssh-keygen\fR(1), \fBssh-http-proxy-connect\fR(1),
-\fBssh-socks5-proxy-connect\fR(1), \fBtelnet\fR(1), \fBsshd\fR(1M),
-\fBssh_config\fR(4), \fBsshd_config\fR(4), \fBattributes\fR(5),
-\fBgss_auth_rules\fR(5), \fBkerberos\fR(5), \fBprivileges\fR(5)
-.sp
-.LP
-\fIRFC 1928\fR
-.sp
-.LP
-\fIRFC 4254\fR