Table of Contents

NAME

SSLrcp - remote file copy

SYNOPSIS

SSLrcp [-s rcp] [-z sslopt] [-pr] file1 file2 SSLrcp [-z sslopt] [-pr] file ... directory

DESCRIPTION

SSLrcp is rcp implemented on top of the Secure Socket Layer (SSL). Unlike rcp authentication is by means of digitally signed X509 certificates.

SSLrcp copies files between machines. Each file or directory argument is either a remote file name of the form ``rname@rhost:path'', or a local file name (containing no `:' characters, or a `/' before any `:'s).

-z
The -z option takes arguments like cert=file, key=file and verify=n, it is the same as in SSLtelnet, SSLrsh, and stelnet. By default SSLrcp looks for its certificate file via the environment variable SSL_CERT.
-p
The -p option causes SSLrcp to attempt to preserve (duplicate) in its copies the modification times and modes of the source files, ignoring the umask. By default, the mode and owner of file2 are preserved if it already existed; otherwise the mode of the source file modified by the umask(2) on the destination host is used.
-r
If any of the source files are directories, SSLrcp copies each subtree rooted at that name; in this case the destination must be a directory.
-s
Normally SSLrcp uses rcp(1) as its server. On some systems (HP-UX for one) rcp does not cope with being run via a socketpair(2). The -s option allows SSLrcp to nominate an alternative server (eg itself). To avoid this problem.

If -z proxy=url is given or one of the environment variables sshell_proxy,https_proxy,http_proxy is set, then ssl_rcmd(3) will connect to the HTTP proxy described by the url and ask it to connect to host. See ssl_rcmd(3) for details.

If path is not a full path name, it is interpreted relative to the login directory of the specified user ruser on rhost, or your current user name if no other remote user name is specified. A path on a remote host may be quoted (using \, «, or `) so that the metacharacters are interpreted remotely.

SSLrcp will prompt you for the password that unlocks your certificate's private key (if need be).

SEE ALSO

rcp(1), SSLrsh(1),

HISTORY

The rcp utility appeared in 4.2BSD.

The SSLrcp utility described here is derrived from the 4.4BSD version by Simon J. Gerraty.

The SSL implementation used is SSLeay by Eric Young <eay@mincom.oz.au> via sjg's libsslfd.

BUGS

Doesn't detect all cases where the target of a copy might be a file in cases where only a directory should be legal.

Is confused by any output generated by commands in a .login, .profile, or .cshrc file on the remote host.

Table of Contents