The general crypto digest design pattern of "start-update-complete" is that the result is a digest of the concatenation of all the "update" messages, not a digest of the last message.
On 6/6/2015 7:02 PM, Massimo Gaggiano wrote: > > I create an "HASH_SHA1" object and update its value two times, > consecutively. Finally I get the hash value, only after the second > update. Though I don't know what does this digest come from. > > Can you give me any explanation? > > I did expect that the final hash value was the second input value's > digest but, evidently, I'm wrong. ------------------------------------------------------------------------------ _______________________________________________ TrouSerS-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/trousers-users
