Re: Scripting FTP in a CL program

[Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>]

James,

You could use SSH, that would easily answer your security issues.  But I 
have a feeling you'll want to run this on releases too old for SSH.

FTPAPI might be a solution for you.  It's my own implementation of FTP, 
but it's a set of procedures in a service program, and you pass the data 
to them directly.  (No need for a script file.)

But, if you're doing plain FTP, then I think you should be worried about 
much bigger and more severe security exposures than a file sitting in 
QTEMP.  (Unless you're using a VPN or something to protect yourself?)



On 12/9/2010 3:36 PM, James H. H. Lampert wrote:
> rob@xxxxxxxxx wrote:
> > Create the script file in qtemp from encrypted data.
>
> Huh????
>
> Let me restate the scenario, in a bit more detail:
>
> Customer Universal Foobar has a dozen AS/400s scattered around the
> planet, some of them non-LPAR-able, some of them with a single LPAR,
> some of them with multiple LPARs.
>
> They have just downloaded Frobozz to one of those boxes, and they're
> tickled pink with it. So they want to put it on all their boxes.
>
> The idea here is to provide them with an easy way of doing this. The
> obvious way to script FTP would be to build the script in a member of a
> PF-SRC in QTEMP. But of course, for at least slightly longer than the
> duration of the FTP connection, the user doing this will have a user-ID
> and password sitting in his or her job's QTEMP, and if the propagation
> program abends without signing off the job, there's no guarantee that if
> that user walks away from the terminal for two minutes without signing
> off, some schmuck won't take a quick peek at that source member.
>
> --
> JHHL