[llvm-foundation] Fwd: Re: [llvm-dev] Bugzilla invalid certificate issues

[Tanya Lattner via llvm-foundation]

bugzilla has been updated.

llvm.org as a whole is next but its a bigger task due to SVN and we are making sure its done correctly as SVN cert changes are not fun.

-Tanya

> On Feb 10, 2017, at 4:04 PM, Philip Reames via llvm-foundation <llvm-foundation at lists.llvm.org> wrote:
> 
> Probably needs attention from the board ASAP
> 
> -------- Forwarded Message --------
> Subject:	Re: [llvm-dev] Bugzilla invalid certificate issues
> Date:	Fri, 10 Feb 2017 17:45:05 -0500
> From:	James Y Knight via llvm-dev <llvm-dev at lists.llvm.org> <mailto:llvm-dev at lists.llvm.org>
> Reply-To:	James Y Knight <jyknight at google.com> <mailto:jyknight at google.com>
> To:	Eric Fiselier <eric at efcs.ca> <mailto:eric at efcs.ca>, Tanya Lattner <tanyalattner at llvm.org> <mailto:tanyalattner at llvm.org>
> CC:	LLVM Developers Mailing List <llvm-dev at lists.llvm.org> <mailto:llvm-dev at lists.llvm.org>
> 
> +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.
> 
> But, now, it's basically an emergency...the warning has made the https parts of the site effectively inaccessible to normal users running Chrome.
> 
> A couple people have mentioned that llvm.org <http://llvm.org/> 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.
> 
> Is there some difficulty with buying a new certificate?
> 
> 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?
> 
> 
> 
> On Fri, Feb 10, 2017 at 4:28 PM, Eric Fiselier via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
> Hi all,
> 
> 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.
> 
> What would it take to fix this?
> 
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev <http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev>
> 
> 
> <Attached Message Part.txt>_______________________________________________
> llvm-foundation mailing list
> llvm-foundation at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-foundation

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-foundation/attachments/20170212/e05f5070/attachment.html>