pscp, psftp and plink ports for RISC OS
---------------------------------------

pscp is a secure copy utility, and psftp is a secure file transfer utility -
these do much the same thing with different interfaces.  plink is a secure
means of running commands on a remote server.  All use the Secure Shell (ssh)
protocol to do their work, and the versions supplied support both SSH v1 and
SSH v2 with several public and private key encryption schemes.  plink also
provides X11 and port forwarding which allow secure connections between two
machines, and the ability to run commands on the remote machine.  Both
password and key authentication are supported.  plink also provides a basic
SSH terminal interface, though this is not supported.

The following ports are based on sources from PuTTY, a Windows SSH client. 
For what they do and documentation on using them see the PuTTY website at
http://www.chiark.greenend.org.uk/~sgtatham/putty/
and/or the supplied documentation.

They support Maarten Bezemer's key generator and agent programs, which can be
found at http://home.student.utwente.nl/m.m.bezemer/indexuk.htm (in the CVS
section).  Key files are the same format as those used by PuTTY under
Windows.

They have only been lightly tested on RISC OS, so these RISC OS ports should
be considered of alpha quality (the Windows/Unix versions from which they are
derived are of alpha quality).  They require the CryptRandom module from
http://www.markettos.org.uk/riscos/crypto/

Release notes
-------------

This version is based on PuTTY code checked out of CVS on 29 November 2003. 
Minimal changes have been applied to it.  To this end there may be a few RISC
OS incompatibilities.  Notably RISC OS full pathnames such as:
adfs::Fish.$.Some.File
won't work in pscp because PuTTY assumes you're trying to access a file on a
machine called 'adfs' (the normal (p)scp syntax is user@host:/path/name).  A
workaround is to use relative pathnames instead.

It is assumed that your Choices: and Choices$Write paths are on a filing
system which can cope with greater than 10 character filenames.  You can use
saved settings files from other PuTTY platforms by putting them into
Choices:Crypto.PuTTY.sessions - replace any '.' characters in the filenames
with '=2E' (and other punctuation characters similarly with their hex code). 
Then invoke psftp, pscp or plink with the session name instead of a host to
connect to.  Default settings can be stored in
Choices:Crypto.PuTTY.sessions.Default=20Settings

It is compiled with Norcroft C and linked with UnixLib from the GCC 3.3
source tree.  Whilst there are minimal changes to the PuTTY sources, a
source tree is provided to save having to track the PuTTY tree.  It should be
simple to do 'cvs update' to get the latest version.

To build the tools, GNU make is required.  Get hold of GCC 2.95.4 or
later and make sure !GCC has been seen by the Filer, change to the PuTTY.unix
directory and do:

 gccbin:make -f Makefile.gtk

Newer versions (if any) can be found at
http://www.markettos.org.uk/riscos/crypto/ (do not be alarmed if this
redirects to www.chiark.greenend.org.uk; this is deliberate and not a cause
for security concern).  The porter can be contacted at theo@markettos.org.uk
- this should be your first point of contact to report bugs rather than the
PuTTY team.

Theo Markettos
theo@markettos.org.uk
http://www.markettos.org.uk/

28 January 2004
