The issue with the Google Chromium web browser reporting valid certificates as “unsafe” has been resolved today with an update to Chromium.
Update, 2016-11-20: We’ve posted a commentary about this on our blog.
The issue with the Google Chromium web browser reporting valid certificates as “unsafe” has been resolved today with an update to Chromium.
Update, 2016-11-20: We’ve posted a commentary about this on our blog.
We are aware that s small subset of users of the Chromium web browser may receive the following error when trying to access websites and control panels via HTTPS that use the *.niner.net certificate:
Your connection is not private
Attackers might be trying to steal your information from cp31.niner.net (for example, passwords, messages or credit cards). NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED
(cp31.niner.net will be replaced by whatever domain you are trying to access.)
If you click the “ADVANCED” link you will see the following additional information:
The server presented a certificate that was not publicly disclosed using the Certificate Transparency policy. This is a requirement for some certificates, to ensure that they are trustworthy and protect against attackers.
This is a bug in Google Chromium, not a problem with our certificate.
Until Google fixes this bug we recommend using a better web browser (e.g., Firefox), or clicking the “Proceed to cp31.niner.net (unsafe)” link that is revealed when you click “ADVANCED” as described above. Clicking the “unsafe” link is indeed safe in this case. Even very big and very busy websites — such as Yahoo and Flickr for example — are currently affected by this bug.
The SSL certificate has been replaced on all servers. If you still get errors, please restart the program in question or, if necessary, restart the machine or device.
If you need any assistance, please contact NinerNet support. Thank-you.
The SSL certificate was upgraded on server NC027 at 10:09 UTC. This covers email services. We’ll be replacing the expired certificates on other server and control panels shortly too.
You may need to restart email programs and web browsers for the new certificate to be recognised. Again, we apologise for the inconvenience.
Our wildcard SSL certificate for *.niner.net has expired in some time zones. It will be updated within the hour and an update posted here.
Our apologies for the delay.
We have completed the maintenance to mitigate against exploitation of the POODLE vulnerability.
Because the effects of this maintenance could potentially be wide-ranging, please contact support if you have any issues with connecting over a secure connection to any of our servers. We don’t believe there will be any issues with web (HTTPS) connections, but there may be with some email (SMTP, IMAP and POP) connections by older email programs. That said, an exploit against this vulnerability has only been demonstrated using JavaScript and a web browser, so email connections (even if using SSLv3) are not generally considered to be at risk.
Thanks for your patience during this maintenance.
UPDATE, 2014-10-24: Please read some details on this maintenance, and learn more about SSL and TLS and email security, on our corporate blog.
The maintenance described in our last post is under way, but we are running into some issues that are delaying completion. While there may be sudden and unexpected interruptions in some services for some clients, we are aware of them and are working on them. If necessary, we will revert to old configurations while we re-evaluate the new configurations recommended to defend clients against the POODLE vulnerability.
Thank-you for your patience.
We will be conducting maintenance this weekend to address the above noted vulnerability. Please read more details about this on our corporate blog.
We have solved the issue with the new NinerNet SSL certificate not fully propagating to all servers. All SSL web and email connections should now be using the new SSL certificate, which expires in 2015.
If you are having any issues, please restart your computer to ensure that all software on the computer uses the new SSL certificate. If you still have problems, please contact NinerNet support with a full description of the error message you are seeing.
Thank-you for your patience.
We are aware that the new NinerNet SSL certificate has not properly propagated to all servers. We are working to fix this and will post an update here as soon as we believe the issue has been resolved.
In the meantime it is usually possible to override any warnings and continue with whatever you are doing.
Systems at a Glance:
| Loc. | System | Status | Ping |
|---|---|---|---|
| NC023 | Internal | Up? | |
| NC028 | Internal | Up? | |
| NC031 | Internal | Up? | |
| NC033 | Operational | Up? | |
| NC034 | Internal | Up? | |
| NC035 | Operational | Up? | |
| NC036 | Operational | Up? | |
| NC040 | Internal | Up? | |
| NC041 | Operational | Up? | |
| NC042 | Operational | Up? |
Subscriptions:
Search:
Recent Posts:
Archives:
Categories:
Links
Tags:
Resources:
On NinerNet: