scp (as part of the secure suite of 'stuff' that includes ssh and sftp)
doesn't work (is unlikely to ever work on) mpe.  (if someone had a lot of
time on their hands and had intimate knowledge of *nix porting there's a
remote possibility I think.)

jeff vance wrote a ftp script (was it called sftpput) that used the posix
program 'crypt' the en-/de-crypt files leaving an mpe system.  (if the
destination system was also mpe, the file would be automatically decrypted
upon delivery...and I wrote a very simple decryption shell script for *nix).


if all that you're looking for is 'push' (from mpe) functionality, sftpput
should work for you, imo.

here's the beginning lines from sftpput:

PARM localfiles=? remotesystem=? remoteuser=* remotedir=* encrypt=true &
     remoteSysT="MPE/IX" remSysHasCrypt=true entry=main
#
# This script transfers, via FTP/iX, "localfiles" from the host MPE system
to
# the "remotesystem". Depending on the "encrypt" parameter and the type of
# file (needs to be ASCII) the file(s) may be encrypted, via the POSIX crypt
# utility, before being transferred. If the remote system is an MPE system a
# job will be streamed, via the 'site stream' FTP command, which
automatically
# decrypts the file. If the remote system is not an MPE system then the file
# needs to be decrypted manually: $crypt key <filename.enc >finalFilename
# The key is FTP'd in its own file named "FileName.key".
#
# To force this script to evaluate the remote system type enter "*" as the
# value of the 'remoteSysT' parm. An extra FTP run is necessary in this
case.
#
# FTP PASSIVE mode is used to increase the chances of being able to connect
# through client firewalls.
#
# This script is sensitive to the existence of the NETRC file, which
provides
# automatic logins to remote systems. If NETRC exists, FTP logs-in using the
# first entry matching the 'remotesystem' name. Thus, the 'remoteuser' parm
is
# typically ignored.  More on NETRC can be found in the notes section.
#
# A user-settable variable, _SFTP_DEBUG, can be set to true to cause this
# script to display diagnostic messages to $STDLIST. If this variable is set
# to false or missing, the script displays fewer messages (but still some).
#
# Parameters are defined in the HELP section near the end of this script.
#
# There are important notes on NETRC, crypt, and IO redirection at the end
of
# this file.

     - d

---
Donna Hofmeister
Allegro Consultants, Inc.
408-252-2330


> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On
> Behalf Of John MacLerran
> Sent: Saturday, January 31, 2009 12:29 PM
> To: [log in to unmask]
> Subject: [HP3000-L] SCP on MPE 7.5?
> 
> Dear hp3000-l
> 
> A while back, there were postings about using sftp and scp on MPE. I
> can't
> remember what the final verdict was, except that I remember someone
> posting
> that MPE can be an scp client, and that the code was available on jazz.
> Now
> that jazz is gone, is it still possible to get the code? How?
> 
> What, exactly, is possible wrt using scp on MPE? I'm presuming that, by
> using
> the term 'client', that you can't log in to another host and scp a file
> 'into' MPE,
> but that you can log in to MPE  and scp files both in from  and out to
> another
> host (i.e, connecting from MPE to the other box with the other box
> acting as a
> server).  Is my understanding basically correct? Or does the term
> 'client' mean
> something else altogether?  Does the jinetd job have to be running for
> the
> client to work?
> 
> I'd appreciate hearing from anyone who has experience with setting it
> up and
> making it work.
> 
> We're on MPE 7.5 PP2
> 
> Thanks!
> 
> -john maclerran
> [log in to unmask]
> 
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *