Peter,

The openX() funcs are *nix based, and NT is very different in these
areas, so my code probably won't help much, and may take you down the
long and winding road 8-((. 

<muse> All our automation is nix based for reliability and manageability
- you might consider a Linux box 8-)? but that is an even longer
road..., then again, commercial support for PGP is no longer available,
and OpenGPG is being much more actively maintained... 8-) </muse>

FWIW we use these NT cmd commands to PGP on NT:

export PGPPASSFD=0
pgp -es data.txt receiver@somewhere -o data.txt.pgp -u me@here <
password.txt

you might consider making passwd.txt a transient file created on the fly
by your script and erased afterwards. Your script would need some way of
knowing what the passphrase is.

regards
Jeff

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] 
> Sent: 25 September 2002 16:20
> To: Jeff AA
> Cc: [EMAIL PROTECTED]
> Subject: RE: Programming pipes to and from another program
> 
> 
> 
> 
> >If *nix, look at help for the open3 function. Attached as a 
> text file is
> >
> >the little run class that I use to do this.
> >
> >Here is an example of how to use this class to encapsulate GPG, where
> >the passphrase gets written to stdin of the child process, and the
> >results are reaped from the childs stderr and the decrypted contents
> >from the childs stdin.
> >[snip]
> 
> Jeff,
> 
> This is exactly the kind of process I'm having trouble with!  PGP
> encription.  Unfortunatly, I'm forced to work on W2K.  I 
> haven't had much
> luck with IPC::Open2, but I'll see if I can adapt this fine code.
> 
> Thanks for the responce,
> Peter
> 
> 
> 
> 
> 
> 


-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to