Just a heads-up.
Clicking "Nightly Builds" on the Trinity web site menu bar results in an SSL Error:
"The site's security certificate is not trusted!
You attempted to reach quickbuild.pearsoncomputing.net, but the server presented a certificate issued by an entity that is not trusted by your computer's operating system. This may mean that the server has generated its own security credentials, which Chromium cannot rely on for identity information, or an attacker may be trying to intercept your communications. You should not proceed, especially if you have never seen this warning before for this site."
It's invoked because https is specified for access to the nightly builds; is this necessary?
Also, I can't help thinking that an unqualified certificate is worse than useless, so why does it even exist?
LeeE
Just a heads-up.
Clicking "Nightly Builds" on the Trinity web site menu bar results in an SSL Error:
"The site's security certificate is not trusted!
You attempted to reach quickbuild.pearsoncomputing.net, but the server presented a certificate issued by an entity that is not trusted by your computer's operating system. This may mean that the server has generated its own security credentials, which Chromium cannot rely on for identity information, or an attacker may be trying to intercept your communications. You should not proceed, especially if you have never seen this warning before for this site."
It's invoked because https is specified for access to the nightly builds; is this necessary?
Also, I can't help thinking that an unqualified certificate is worse than useless, so why does it even exist?
LeeE
It mainly exists because the Launchpad software which QuickBuild is built on cannot operate without a certificate. To make matters worse, it won't work over plain HTTP either.
I have had plans for some time to investigate a free "real" certificate for that site, but never found the time to do so.
Tim
-
leee -
Timothy Pearson