[collectd] Assertion crash in collectd 5.2.1 / libgcrypt 1.5.2
teichm at in.tum.de
Mon Jun 24 22:24:16 CEST 2013
a friend of mine thinks the problem lies within the crypto code of
collectd and suggested a rewrite to use aes-ctr + hmac-sha1 or even
better aes-ocb or nacl.
just his two cents… ;)
Am 18.06.2013 08:38, schrieb teichm:
> On our collectd 5.2.1 from the Debian Package 5.2.1-1 we encountered an
> assertion crash from libgcrypt11 1.5.2-1 that occurs aproximately once a
> day on random conditions.
> I do not know, if collectd is using libgcrypt wrong or if it is a bug in
> It seems, ath_install was called with the first argument beeing NULL. At
> least i have no other explanation of why this codepath would be reachable.
> Since i am also working on my Bachelor's thesis at the moment in which I
> am developing Monkey, a new automated bug reporting system, i generated
> a report for your convenience:
> If you are interested in the Debugging System, you can find more
> information on:
> Also i have a survey (or rather ‘experiment’) running, in which you will
> get three different crash reports (stack trace, stack trace + *life gdb
> session* on a core dump and of course one generated from Monkey) and try
> to find the respective bug.
> You can participate here:
> collectd mailing list
> collectd at verplant.org
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 4826 bytes
Desc: S/MIME Kryptografische Unterschrift
More information about the collectd