Start using Firefox 3 and you get new insights.
openssl s_client -connect www-949.ibm.com:443
Tells me the same :-)
FF2 tells you the same thing. Using self signed certs in and of itself is not necessarily a bad thing. Is this a customer facing site?
i thought that Mozilla and Opera and Microsoft agreed on the color scheme for certificate error so users would have the same noticiation.
does it turn red if you continue after the warning ?
There is no need to use Firefox 3 to get this not always helpful message. The major problem is that hardly anybody sees and uses the offered hotspot "exception" ! That is the same situation with IE or Opera.....
And that is why companies like Verisign and Thawte have a rather simple and very successful business modell: They just sell the evidence of conformity with certificates stored in browser software.
@Claus: You're correct. In fact, the dialog is technically incorrect - a certificate is not "invalid" simply because it is self-signed. This message is needlessly alarmist.
its properly considered invalid, because the connection may have been infiltrated by a man-in-the-middle attack.
Only if you would be able to verify the authenticity, it would even provide the higher level of integrity over an official certificate.
I agree with David - that the connection may have been infiltrated does not mean that the certificate is invalid. It's good that FF show's its suspicion, but to say the certificate is invalid is just not correct.
From a client perspective, the trustworthiness of certificates rely solely on some bunch of chaining mumbo-jumbo. As roots of some authorities are stored on your system already, only these are considered valid, and so their descendants.
Unlike self-signed certs. They are considered invalid, because no reference is found, unless added to the trust-store manually. This dialog-phrase sure makes sense to users.
Much more important to me: I Heart the new look!
Britta Fischer on Surface 3 (4G LTE) is coming at 16:21
Johannes Matzke on Surface 3 (4G LTE) is coming at 14:32
Ingo Seifert on Surface 3 (4G LTE) is coming at 14:10
Markus Dierker on Surface 3 (4G LTE) is coming at 12:29
Frank Müller on Umgekehrte Alex-Warnung at 11:21
Davy Vanherbergen on Umgekehrte Alex-Warnung at 23:50
Ian Bradbury on The Ello Bill of Rights at 23:17
Gerhard Poul on Surface 3 (4G LTE) is coming at 21:22
Stephan Meurer on Beats 1 stream URLs at 18:39
Amy Blumenfield on Beats 1 stream URLs at 18:34
Volker Weber on Microsoft could write off billions on Nokia deal at 17:49
Daniel Haferkorn on Umgekehrte Alex-Warnung at 12:27
Ingo Seifert on Microsoft could write off billions on Nokia deal at 11:32
Volker Weber on Withings imports from Fitbit at 11:06
Volker Weber on Umgekehrte Alex-Warnung at 09:33
Daniel Haferkorn on Umgekehrte Alex-Warnung at 09:29
Chris Hudson on Withings imports from Fitbit at 07:34
Jochen Kattoll on COBO - you are going to hear this at 00:40
Andrew Magerman on Apple Music on SONOS :: How soon is ASAP? at 23:37
Kevan Emmott on Apple Music on SONOS :: How soon is ASAP? at 22:45
Max Nierbauer on Microsoft could write off billions on Nokia deal at 22:34
Jörg Michael on Apple Watch Sapphire vs Glass Display Shoot-Out at 16:23
David Eyre on Umgekehrte Alex-Warnung at 23:46
Volker Weber on Umgekehrte Alex-Warnung at 22:06
David Eyre on Umgekehrte Alex-Warnung at 21:58