3 ms·
No panic, just if you use IE read this: http://en.wikipedia.org/wiki/Server_Name_Indication#Support http://en.wikipedia.org/wiki/Server_Name_Indication#Support
by Zenst 14y ago
No panic, just if you use IE read this: http://en.wikipedia.org/wiki/Server_Name_Indication#Support http://en.wikipedia.org/wiki/Server_Name_Indication#Support
Real browsers like Opera, Chrome, firefox.... all good
my bad and edited my panic away.
Thanks dchest for being more awake than I.
- dchest 14y agoWhat problem? What browser and OS do you use?
- Zenst 14y agoOn my other computer - and sadly had IE (latest and patched IE 9) running. Now checked with Opera, firefox and Chrome and they get issued a different certificate - most odd and probably a anti IE thing. IE seems to get a certificate for www.131002.net, others get certificate for that site. Different expiry dates and details so again probably a anti IE script of some form.
- dchest 14y agoAha, it's because IE on WinXP doesn't support SNI (http://en.wikipedia.org/wiki/Server_Name_Indication#Support http://en.wikipedia.org/wiki/Server_Name_Indication#Support). Unfortunately, there's no way for servers to work around this other than putting different domains on different IP addresses.
- Zenst 14y agoBox in question has Vista, and did have TLS disabled. Still I'll blame microsoft.
- dchest 14y agoI only found this about Windows 7 / IE8 SNI problem, maybe it'll help http://answers.microsoft.com/en-us/ie/forum/ie8-windows_7/sni-support-not-working-in-ie-8-windows-7/de189384-cefb-4234-ab95-36a7a5e3d5bc http://answers.microsoft.com/en-us/ie/forum/ie8-windows_7/sn...
- Zenst 14y agoI edited the original post to highlight my stupidity and many thanks for being more awake than I. I'll have a read thru that when a bit more awake but moral being. Don't use IE, even if you are using one of your lesser computers :|. Again thank you.
- marshray 14y agoDid you make customizations to end up with TLS disabled in IE on Vista? Or did you end up this way fom default settings?
- Zenst 14y agoBy default TLS 1.0 is enabled, I disabled it myself ages ago as other more robust options were supported and whilst extensions have been added at the time I felt it was for the best. Worked fine for me until this moment at least when I have used that particular box, but nice to always learn. in short - no default is TLS 1.0 on, I changed it to disabled for TLS 1.0 and left SSL 2.0 and 3.0 enabled as they are by default.
- marshray 14y agoSSL 2.0 is old and busted. You ought to disable it. SSL 3.0 is all-but identical to TLS 1.0.
- CodesInChaos 14y agoWhy do you disable the newest protocol version (TLS 1.0 is essentially SSL 3.1) but keep the older versions? I'd enable SSL 3.0 and TLS 1.x, but disable SSL 2.0 since it's old and broken.
- deleted 14y ago[deleted]
- stephengillie 14y agoThe certificate looks good to my browser. shrug It's a StartCom intermediate certificate, good from 2/5/13 to 2/7/14, and the connection is encrypted with RC4_128. So says Chrome...
- Zenst 14y agoYes yoru spot on, just looked into it more and it is TLS 1.0 on chrome and I disabled that upon my IE browser, so may be the issue and explains why. Though as different certificate my initial thoughts are still with some anti IE script of some form - IE gets cert for differnt site and also from same issuing authority. No panic.