Newbie Q: decryption

Joseph Oreste Bruni jbruni at
Tue Feb 27 02:56:39 CET 2007

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.


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 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
> Gnupg-users at

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2508 bytes
Desc: not available
Url : /pipermail/attachments/20070226/8d706bb4/attachment.bin 

More information about the Gnupg-users mailing list