<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Bugzilla will be fixed very soon.<div class=""><div class=""><br class=""></div><div class="">-Tanya</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Feb 10, 2017, at 4:27 PM, Chris Matthews <<a href="mailto:chris.matthews@apple.com" class="">chris.matthews@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div id="bloop_customfont" style="font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; margin: 0px;" class="">Letsencrypt only offers domain validation certs. I think an EV cert would be more appropriate for<span class="Apple-converted-space"> </span><a href="http://llvm.org/" class="">llvm.org</a>.</div><div id="bloop_sign_1486772591721501952" class="bloop_sign" style="font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"></div><br style="font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><p class="airmail_on" style="font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">On February 10, 2017 at 2:45:22 PM, James Y Knight via llvm-dev (<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>) wrote:</p><blockquote type="cite" class="clean_bq" style="font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;"><span class=""><div class=""><div class=""></div><div class=""><div dir="ltr" class="">+1. Chrome been warning about the certificate for a year or so now, with steadily increasing severity. Would've been nice to fix it back then.<div class=""><br class=""></div><div class="">But, now, it's basically an emergency...the warning has made the https parts of the site effectively inaccessible to normal users running Chrome.</div><div class=""><br class=""></div><div class="">A couple people have mentioned that<span class="Apple-converted-space"> </span><a href="http://llvm.org/" class="">llvm.org</a><span class="Apple-converted-space"> </span>was "not working" to me recently. And, I hadn't upgraded Chrome yet, so I didn't understand what they were saying at the time. But, now I have: the full page blocking warning basically makes the site appear inaccessible, unless you're looking very closely.<div class=""><br class=""></div><div class=""><div class="">Is there some difficulty with buying a new certificate?</div></div><div class=""><br class=""></div><div class=""><div class="">Switching to letsencrypt would be best, and free, of course, but that takes a little more infrastructure work to set up, and I'd understand if maybe nobody's had the time to do that yet. Which is fine -- but in the meantime, can someone just pay for a new certificate from any of the standard CAs?</div></div><div class=""><br class=""></div><div class=""><br class=""></div></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Fri, Feb 10, 2017 at 4:28 PM, Eric Fiselier via llvm-dev<span class="Apple-converted-space"> </span><span dir="ltr" class=""><<a href="mailto:llvm-dev@lists.llvm.org" target="_blank" class="">llvm-dev@lists.llvm.org</a>></span><span class="Apple-converted-space"> </span>wrote:<br class=""><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;"><div dir="ltr" class="">Hi all,<div class=""><br class=""></div><div class="">The bugzilla has always had an invalid certificate, but in the past week or so Google Chrome has begun treating it as a dangerous site. Meaning every time a new page is loaded a full-page warning splash appears and users have to click through it. This is getting really frustrating.</div><div class=""><br class=""></div><div class="">What would it take to fix this?</div></div><br class="">______________________________<wbr class="">_________________<br class="">LLVM Developers mailing list<br class=""><a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a><br class=""><a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank" class="">http://lists.llvm.org/cgi-bin/<wbr class="">mailman/listinfo/llvm-dev</a><br class=""><br class=""></blockquote></div><br class=""></div>_______________________________________________<br class="">LLVM Developers mailing list<br class=""><a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a><br class=""><a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" class="">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a></div></div></span></blockquote></div></blockquote></div><br class=""></div></div></body></html>