[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openssl-dev
Subject:    Re: [openssl-dev] Fuzzer Patch(es)
From:       Tom Ritter <tom () ritter ! vg>
Date:       2016-08-27 21:59:48
Message-ID: CA+cU71kFZc-J+N1QZAa4+k+jqmTpHKmLW4OYoXH1CrmXr2CeRQ () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On 26 August 2016 at 11:33, Benjamin Kaduk <bkaduk@akamai.com> wrote:

> - Because ossltest cooks MD5 to output a constant value, OpenSSL's RNG
> becomes constant.
>
>
> Is it specifically MD5 and not SHA1?  That would be worrisome, as I
> thought rand_lcl.h would be setting up for USE_SHA1_RAND by default, not
> md5.
>

No, that was an offhand comment - it produces a constant output for most
hash functions: MD5, SHA-1, SHA256, 384, and 512.

-tom

[Attachment #5 (text/html)]

<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 26 August \
2016 at 11:33, Benjamin Kaduk <span dir="ltr">&lt;<a href="mailto:bkaduk@akamai.com" \
target="_blank">bkaduk@akamai.com</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000"><span \
class=""><blockquote type="cite"><div dir="ltr"><div>- Because ossltest cooks MD5 to \
output a constant value,  OpenSSL&#39;s RNG becomes constant. </div>
      </div>
    </blockquote>
    <br></span>
    Is it specifically MD5 and not SHA1?   That would be worrisome, as I
    thought rand_lcl.h would be setting up for USE_SHA1_RAND by default,
    not md5.<br></div></blockquote><div><br></div><div>No, that was an offhand \
comment - it produces a constant output for most hash functions: MD5, SHA-1, SHA256, \
384, and 512.</div><div><br></div><div>-tom</div></div></div></div>



-- 
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev


[prev in list] [next in list] [prev in thread] [next in thread]