"out of secure memory while allocating 4316 bytes"

Werner Koch wk@gnupg.org
Wed Jul 4 11:55:01 2001

 || On Wed, 4 Jul 2001 09:08:16 +0000
 || Jim Breton <jamesb-gpg@alongtheway.com> wrote: 

 jb> After reading that, I tried my own and indeed, this does seem to only
 jb> occur if I fail to type my passphrase correctly the first time.

Thanks, I will look into it.  It seems that some memory is not freed

Workaround is to look for secmem_init(16384) in g10/g10.c and increase
the value.

 jb> P.S. I have not been able to find a good, detailed description of what
 jb> "m-guard" _actually_ does, is this information available somewhere?

I puts markers just before the begin and after the end of an allocated
memory block and checks on free whether they have been overwritten.
It also registers the file and line number so you can better locate
the malloc call.

I am going to remove this in the future because there are now
libaries which do better job.

Werner Koch        Omnis enim res, quae dando non deficit, dum habetur
g10 Code GmbH      et non datur, nondum habetur, quomodo habenda est.
Privacy Solutions                                        -- Augustinus