Media - development & use
Objet : Re: [Live-devel] use of unitialized memory in our_MD5End
In any case, this isn't a concern, because we're using MD5 here to generate a
'pseudo-random' value. It doesn't matter if some of the memory that MD5 reads
happens to be &#
In any case, this isn't a concern, because we're using MD5 here to generate a
'pseudo-random' value. It doesn't matter if some of the memory that MD5 reads
happens to be 'uninitialized'.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
to maintain
Best Regards,
Michel.
[@@THALES GROUP RESTRICTED@@]
De : live-devel-boun...@ns.live555.com
[mailto:live-devel-boun...@ns.live555.com] De la part de Ross Finlayson
Envoyé : vendredi 20 janvier 2012 15:18
À : LIVE555 Streaming Media - development & use
Objet : Re: [Live-d
> What do you think ?
I think that "valgrind" is incorrect in this case. In the implementation of
"Authenticator::setRealmAndRandomNonce()", both fields of the "seedData"
structure are initialized. (The "timestamp" field is initialized via the call
to "gettimeofday()"; the "counter" field is
Hi,
Valgrind report use of memory that is not initialized in our_MD5End.
Use of uninitialised value of size 8
(see: http://valgrind.org/docs/manual/mc-manual.html#mc-manual.uninitvals)
at 0xE5558F: our_MD5End (our_md5hl.c:34)
by 0xE55751: our_MD5Data (our_md5hl.c:67)
