Why firefox warns and IE doesnt't ?
Greeting's
I don't know how many of you have either had or currently do face this problem. Whenever you try to log-into some page's in Microsoft site's or even some time's hotmail using Firefox it gives you an unknown certificate error (security warning) but the same page loads without any problems in IE, no error's no warnings'. Most of us (or at least those who are paranoid) take all the actions possible to find out whats wrong in the PC or fear that they are 0wned anyway after all the online scan's, going through the log's checking for rootkits or even checking with previously taken MD5 or SHA1 of the all the files on the drive nothing comes up.....
SO what wrong here ?
I have been facing this problem a lot and here is the answer (its Microsoft again)
Entire article is too big and has too many picture's to copy so i have given the links to the article's :
But anyway the problem in short is that :
Quote:
So according to the above RFC, Internet Explorer is following a document that is on the Standards Track. Other browsers such as Mozilla have chosen not to implement this option due to some ambiguity in the RFC. You can see more discussion about this here in the Bugzilla entry created on this topic.
Quote:
Now since this page deals with security (specifically web browser) security, it is counterproductive to the mindset we are trying to train people to have to use an SSL certificate that they can't verify. If folks just think to them self "Hey this came from Microsoft's security folks, it should be ok" it sets up reinforcement of ignoring SSL certificate errors.
Quote:
While Internet Explorer is complying with an optional standard as defined by RFC2459, it seems to be the only major browser doing so. I am not saying that they are doing something wrong, just different. The de facto standard way to verify a certificate's authenticity seems to be to either provide the intermediate CA certs along with the server certificate or to require the end-user's web browser to have the required CA certs already installed.
What I see as the potential problem with Microsoft's way of validating the certificate is that it only works for people using Internet Explorer. Anyone using a non-IE browser to go to such SSL-secured pages will get an alert that the certificate can not be verified.
1. http://isc.sans.org/diary.php?storyid=1230&rss
2. http://blogs.msdn.com/larryosterman/...04/148612.aspx
3. https://bugzilla.mozilla.org/show_bug.cgi?id=245609
4. https://bugzilla.mozilla.org/show_bug.cgi?id=245609