Oh yeah, third thing:The "insecure memory" warning just means that the executable probably needs to be setuid-root in order to allocate wired memory. You can ignore this and still use the product. It just means that gpg tried to allocate memory that cannot be swapped to disk and failed due to permissions. Some OS's allow non-root users to allocate a limited amount of wired memory (BSD, OS X) whereas HP-UX does not.
Joe On Feb 26, 2007, at 5:36 PM, Jon Drukman wrote:
A company I'm getting a data feed from sent me a public key and an encrypted file. I want to decrypt it, but I don't know I'm doing. My naive approach is not working: $ gpg --homedir=/var/httpd/keyring --decrypt upc.xml.pgp gpg: WARNING: using insecure memory! gpg: please see http://www.gnupg.org/faq.html for more information gpg: mpi too large for this implementation (40856 bits) the public key is in the file "nf_key". i thought i imported it but i don't how to tell if i did it right, or if it's even the right key for the file. help! -jsd- _______________________________________________ Gnupg-users mailing list [email protected] http://lists.gnupg.org/mailman/listinfo/gnupg-users
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Gnupg-users mailing list [email protected] http://lists.gnupg.org/mailman/listinfo/gnupg-users
