PGP encrypting/decrypting files in Co:Z process

[jbourq]

:? I’m attempting to convert an existing Windows SSH process to Co:Z. The existing process retrieves encrypted (.pgp) files from an outside vendor and also sends encrypted files back to the vendor. I know it seems pointless to encrypt files that are being sent through an already secure sftp tunnel. But I’m trying to see if I can minimize the impact to the vendor if we asked them to create their files as .txt files or to receive ours as .txt files.

In the Co:Z Launcher – User’s Guide, paragraph 5.3, there is an example on sending commands to a Linux server for PGP encryption of MVS datasets along with an example for decrypting as well. I’m familiar with the process for encrypting and decrypting data files in a Windows environment. When I look at your examples, I can’t tell where the Public and Secure Keys are defined.

What makes the most sense? Continuing to do the PGP encryption/decryption or simply create .TXT files instead.

[dovetail]

The example for using PGP on linux uses the open source "gpg" command.

For documentation on using that software see:
https://www.gnupg.org/documentation/manpage.html

[jbourq]

Thank you. The documentation helped.