by Anonymous Coward writes:
on Sunday February 23, 2014 @12:39PM (#46316735)
I don't know. MD5 is no longer considered a collision free hash. It is entirely plausible that the VP9 implementation will output only same MD5, but not same output for a few frames. They should really upgrade to SHA-256 or stronger.
I don't know. MD5 is no longer considered a collision free hash. It is entirely plausible that the VP9 implementation will output only same MD5, but not same output for a few frames.
Really? I think you do not know what you are talking about. There is a higher chance of the sun going nova tomorrow than code output producing same MD5 hashes, by accident.
Documentation is like sex: when it is good, it is very, very good; and
when it is bad, it is better than nothing.
-- Dick Brandon
Faster is not necessarily better: Quality matters. (Score:3, Interesting)
Re: (Score:5, Informative)
Re: (Score:0)
Equivalent or identical?
Re: (Score:3)
Dude. It has the same hash value. What do you think?
Re:Faster is not necessarily better: Quality matte (Score:1)
I don't know. MD5 is no longer considered a collision free hash. It is entirely plausible that the VP9 implementation will output only same MD5, but not same output for a few frames. They should really upgrade to SHA-256 or stronger.
Re: (Score:1)
I don't know. MD5 is no longer considered a collision free hash. It is entirely plausible that the VP9 implementation will output only same MD5, but not same output for a few frames.
Really? I think you do not know what you are talking about. There is a higher chance of the sun going nova tomorrow than code output producing same MD5 hashes, by accident.