26 Apr
2013
26 Apr
'13
9:49 p.m.
On Fri, Apr 26, 2013 at 8:21 PM, Niels Möller nisse@lysator.liu.se wrote:
The current HMAC API assumes that the hashing state is kept per call.
I don't think so, but maybe I misunderstand you (or maybe you have found a bug?).
It seems you're correct, sorry for the noise. I interpreted the _digest() functions of nettle similarly to digest output functions in gcrypt which don't cause a reset of the hash. I should have read the documentation carefully. The current code is thus fine for my usage.
regards, Nikos