LLVM Bugzilla MOVED to bugs.llvm.org

All,

http://llvm.org/bugs has moved to bugs.llvm.org. You will be redirected if you attempted to access via the old URL, but please update your bookmarks as well.

HTTPS access to bugzilla is now updated to a new SSL certificate.

If you experience any problems, please let me know or email llvm-admin@lists.llvm.org

Thank you,
Tanya

Thanks for migrating the bugzilla installation!

I noticed that old https links to llvm.org/bugs still trigger the SHA1 certificate warning, because we still haven’t renewed the main llvm.org certificate. As time goes on, links to the old tracker location will become less common, but all existing links to the LLVM bug tracker are effectively broken. This also affects browsing the main llvm.org web site with https, which is where we post our releases.

Does the LLVM foundation have plans to renew the primary llvm.org SSL certificate?

I definitely support your efforts to migrate LLVM infrastructure away from UIUC, but it might be worth renewing the main certificate now to keep the existing site working.

URLs should redirect to , so people don’t log into the http version by accident. HSTS would also be nice. -Eli

Thanks for migrating the bugzilla installation!

I noticed that old https links to llvm.org/bugs still trigger the SHA1 certificate warning, because we still haven’t renewed the main llvm.org certificate. As time goes on, links to the old tracker location will become less common, but all existing links to the LLVM bug tracker are effectively broken. This also affects browsing the main llvm.org web site with https, which is where we post our releases.

Does the LLVM foundation have plans to renew the primary llvm.org SSL certificate?

I definitely support your efforts to migrate LLVM infrastructure away from UIUC, but it might be worth renewing the main certificate now to keep the existing site working.

The llvm.org SSL certificate will be revoked and a new one will be issued. Because that certificate is used for SVN as well as llvm.org, we would like to keep the disruptions at a minimum for SVN users. SVN is relocating to the new server (where other websites and bugzilla moved to).

UIUC owns the current certificate and instead of going through the path of trying to get it upgraded, it makes sense to just get a new one and revoke the old. But as I mentioned above, keeping our SVN users happy is my priority.

I’ll be sending out an email to communicate the upgrade path for SVN in the next day or 2.

-Tanya

URLs should redirect to , so people don’t log into the http version by accident.

I made this change.

HSTS would also be nice.

Seems reasonable… I’ll see about doing this.

-Tanya

This doesn’t appear to be working: I just tried visiting , and it doesn’t redirect. -Eli

This doesn’t appear to be working: I just tried visiting , and it doesn’t redirect.

I mis-read this. I thought (nonHTTPS) llvm.org/bugs should redirect to https://bugs.llvm.org. Will add the second part.

-Tanya

Hi All,

The bugzilla links of the form [llvm.org/PR](http://llvm.org/PR)*xxxx* are still redirecting to llvm.org/bugs/.… instead of [bugs.llvm.org/](http://bugs.llvm.org/`).

Could we fix this?

/Eric

Hi All,

The bugzilla links of the form `llvm.org/PR*xxxx` *are still redirecting
to
llvm.org/bugs/... instead of `bugs.llvm.org/`.

Could we fix this?

And while at this, maybe also add a redirect for httpS://llvm.org/PR*

Best,
Tobias

> Hi All,
>
> The bugzilla links of the form `llvm.org/PR*xxxx` *are still redirecting
> to
> llvm.org/bugs/... instead of `bugs.llvm.org/`.
>
> Could we fix this?

And while at this, maybe also add a redirect for httpS://llvm.org/PR*

Ping. llvm.org/PR* still redirects to the old URL.

Should be fixed

I’m getting a cert error
https://www.llvm.org

SEC_ERROR_CERT_SIGNATURE_ALGORITHM_DISABLED

Web insperctor says SHA-1 is no longer acceptable as key

The http://llvm.org/PR32147 link correctly re-directs, but the https version (https://llvm.org/PR32147) still hits the certificate error, possibly before redirecting?

Is it possible to fix the httpS version?