Re: Using GNUPG --encrypt problems

[Mark S Waterbury <mark.s.waterbury@xxxxxxxxxxxxx>]

Peter:

Apparently,  QP2TERM does not handle certain "/dev/tty" stuff...

See:
    http://showcase.netins.net/web/iseries/welcome.shtml

for how to get past those issues, to  get it "configured" and  then, 
once configured, you can use gnupg, e.g. from CL via QP2SHELL ...

Hope that helps,

Mark S.  Waterbury

> On 2/9/2017 5:11 PM, Peter Connell wrote:
> I've installed GnuPG for IBM I PASE from Scott Klement's web site.
>
> I was supplied with a file containing the public key of the recipient of the encrypted file.
> Using QP2TERM I successfully imported the public key
>
> gpg --armour --import '/tmp/VedaProd (Veda Prod File Transfer).asc'
> gpg: WARNING: using insecure memory!
> gpg: please see http://www.gnupg.org/faq.html for more information
> gpg: directory `/home/pjctest/.gnupg' created
> gpg: new configuration file `/home/pjctest/.gnupg/gpg.conf' created
> gpg: WARNING: options in `/home/pjctest/.gnupg/gpg.conf' are not yet active during this run
> gpg: keyring `/home/pjctest/.gnupg/secring.gpg' created
> gpg: keyring `/home/pjctest/.gnupg/pubring.gpg' created
> gpg: /home/pjctest/.gnupg/trustdb.gpg: trustdb created
> gpg: key BCC4E7A8: public key "VedaProd (Veda Prod File Transfer) <serverandstorage@xxxxxxxxxxxxxxxxx>" imported
> gpg: Total number processed: 1
> gpg:               imported: 1
>
> It appears that the 'WARNING: using insecure memory' is just that and can be inhibited by adding 'no-secmem-warning' to the gpg.conf file
> Then I confirmed the import by listing the keys
>
> gpg --list-keys
> gpg: WARNING: using insecure memory!
> gpg: please see http://www.gnupg.org/faq.html for more information
> /home/pjctest/.gnupg/pubring.gpg
> --------------------------------
> pub   1024D/BCC4E7A8 2009-11-08
> uid                  VedaProd (Veda Prod File Transfer) <serverandstorage@xxxxxxxxxxxxxxxxx>
> sub   2048g/333FF8CF 2009-11-08
>
> But when I try to encrypt a test file I get the error 'cannot open /dev/tty'
>
> gpg --encrypt --recipient 'serverandstorage@xxxxxxxxxxxxxxxxx' /home/pjctest/test.txt
> gpg: WARNING: using insecure memory!
> gpg: please see http://www.gnupg.org/faq.html for more information
> gpg: 333FF8CF: There is no assurance this key belongs to the named user
> gpg: cannot open `/dev/tty': No such device or address
> $
>
> I can't get past this. Has anyone done this before?
>
> Regards, Peter
>
> ############################################################## This correspondence is for the named person's use only. It may contain confidential or legally privileged information, or both. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this correspondence in error, please immediately delete it from your system and notify the sender. You must not disclose, copy or rely on any part of this correspondence if you are not the intended recipient. Any views expressed in this message are those of the individual sender, except where the sender expressly, and with authority, states them to be the views of Veda. If you need assistance, please contact Veda :- Australia http://www.veda.com.au/contact-us New Zealand http://www.veda.co.nz/contact-veda ##############################################################