out of memory on encrypt
Thu Aug 28 20:36:02 2003
=2D----BEGIN PGP SIGNED MESSAGE-----
On Thursday 28 Aug 2003 1:46 pm, Ross Druker wrote:
> While I appreciate your advice on proper usage of keys and users, that was
> not really my question. I'm trying to get gpg working on AIX. But just =
I know that, but using GnuPG properly at least helps me to know that the er=
message is real rather than an artefact of an incomplete/broken installatio=
> you know, the private key is from someone I work with. They generated the
Sorry, bad excuse!=20
> key on their PC and I imported it into gpg on the AIX system because they
> asked if I could re-use their existing key. I can address the procedural
It's their key?! Not yours?! Generating your own key on the target system i=
much better test of the success or failure of the installation.
> issues you raise later (and they are good points), but if I can't get the
> program to run, they don't do me any good.
Seriously, it'll be much easier to know what it really happening when the=20
GnuPG setup is known to be good. This in turn is easier to know if you are=
using GnuPG properly. Errors like the ones I pointed out don't inspire much=
confidence that the rest of the installation is workable.
So, to solve your out of memory problem: First things first.
1. Can you generate new keys, list all your keys, import and export keys OK?
(You can always delete this test key later, so don't be too fussy about the=
settings, just see if the defaults work.)
Download http://www.codehelp.co.uk/neilwilliams.txt to your home directory =
gpg --import neilwilliams.txt
gpg -a --export 28bcb3e3
gpg -a -e neilwilliams.txt
Gpg will prompt you for the recipient key. Enter your newly generated keyid=
and then a blank line. This way you can decrypt the file later to make sure=
your new secret key is working.
gpg -a -e neilwilliams.txt
You did not specify a user ID. (you may use "-r")
Enter the user ID. End with an empty line:=20
Compare the output and repost.
I've changed to inline signature for this email so you should also be able =
save this to a local file and use:
gpg --verify filename
> So my questions really are:
> Why is gpg bombing?
Could be down to problems in your installation - the above tests should hel=
resolve the doubts. If all the above work, please post more details of the=
> Has anyone else seen this memory problem?
> Has anyone succuessfully run gpg on AIX 5.1?
Now I can't help with the specifics of that last one, but by running the ab=
commands, any error messages will give everyone a solid base to find the=20
solution because all the steps are reproducible.
> Again, here is the tail end of the output:
> > gpg: writing to `testpgp.txt.gpg'
> > gpg: ELG-E/CAST5 encrypted for: "A27627F4 User's Name <User's e-mail
> > gpg: out of memory while allocating 8192 bytes
I'm sure this can be resolved, it just needs a little procedure.
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
=2D----END PGP SIGNATURE-----