<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">While I’m probably not qualified to answer this question in a totally comprehensive way, the following technet article is illuminating if you ever find yourself wondering what SHA1 is still valid for in Microsoft land.</div><div class=""><br class=""></div><div class=""><a href="https://social.technet.microsoft.com/wiki/contents/articles/32288.windows-enforcement-of-sha1-certificates.aspx" class="">https://social.technet.microsoft.com/wiki/contents/articles/32288.windows-enforcement-of-sha1-certificates.aspx</a></div><div class=""><br class=""></div><div class="">Basically, a lot.</div><div class=""><br class=""></div><div class="">-Ryan</div><br class=""><div><blockquote type="cite" class=""><div class="">On Feb 23, 2017, at 9:31 AM, Dave Aitel &lt;<a href="mailto:dave.aitel@gmail.com" class="">dave.aitel@gmail.com</a>&gt; wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">So what is it that breaking SHA1 gets you on Windows boxes?<div class=""><br class=""></div><div class="">-dave</div></div>
_______________________________________________<br class="">Dailydave mailing list<br class=""><a href="mailto:Dailydave@lists.immunityinc.com" class="">Dailydave@lists.immunityinc.com</a><br class="">https://lists.immunityinc.com/mailman/listinfo/dailydave<br class=""></div></blockquote></div><br class=""></body></html>