[collectd] Ohhhh jeeee, libgcrypt 1.4.1 + collectd 4.7.2

[Sebastian Harl]

Hi,

On Mon, Aug 31, 2009 at 05:51:23PM +0200, Florian Forster wrote:
> On Sun, Aug 30, 2009 at 10:31:55PM -0700, Luke Heberling wrote:
> > When using collectd 4.7.2 with libgcrypt 1.4.1 I'm getting an error
> > message: Ohhhh jeeee: operation is not possible without initialized
> > secure memory
[…]
> > upgrading libgcrypt to 1.4.4 (squeeze) fixes the problem, …
> 
> The NEWS.gz of the libgcrypt11-dev package has this to say (regarding
> new stuff in version 1.4.3):
> 
>  * Auto-initialize the secure memory to 32k instead of aborting the
>    process.
> 
> Without knowing what *exactly* is going on it's hard to decide what to
> do against this problem, especially since this kind of problem appears
> to be “fixed” in later versions of the library.

Hrm … from a quick look at the libcrypt documentation I suppose we need
to call gcry_control() using the 'GCRYCTL_INIT_SECMEM' command to
explicitly initialize the secure memory. Sounds like this was required
in libgcrypt 1.4.1 but is handled automatically in later versions.

Cheers,
Sebastian

-- 
Sebastian "tokkee" Harl +++ GnuPG-ID: 0x8501C7FC +++ http://tokkee.org/

Those who would give up Essential Liberty to purchase a little Temporary
Safety, deserve neither Liberty nor Safety.         -- Benjamin Franklin

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
Url : http://mailman.verplant.org/pipermail/collectd/attachments/20090831/2efb4061/attachment.pgp