#21
|
|||
|
|||
Re: i.e. 7
And that's cool. Just that FF is not the end-all be-all. It has holes as well.
>90% of IE's problems are ActiveX related. Skip the free computer checkups and the like and you've solved a majority of the problem. |
#22
|
|||
|
|||
Re: i.e. 7
[ QUOTE ]
And that's cool. Just that FF is not the end-all be-all. It has holes as well. >90% of IE's problems are ActiveX related. Skip the free computer checkups and the like and you've solved a majority of the problem. [/ QUOTE ] I'm glad we found common ground [img]/images/graemlins/smile.gif[/img] |
#23
|
|||
|
|||
Re: i.e. 7
The argument if FF is better the IE is not as clear as most people think from a security perspective, it depends upon what month/year you are talking about as both release security patches. Check out this graph from PC Magazine it seems flaws are on the raise in all web browsers (not good) http://www.pcmag.com/image_popup/0,1...=155130,00.asp ( full article HERE ). I guess we should all use Opera since that passed the Acid 2 test and it is most closely supports the W3C standards but that has its issues as well. All this means is that the internet/web browsing is still not ready for prime time.
Later, WGO |
#24
|
|||
|
|||
Re: i.e. 7
Interesting that nowhere in that article did it compare the number of flaws that allowed code execution w/o user interaction.
That's where IE to my knowledge has never been more secure than FF. A DoS attack that causes FF to crash when viewing a page, or to spike 100% CPU, or go on a memory rampage is annoying. Code execution relinquishes complete control of your system to an unknown 3rd party. I'll take 50 annoyance vectors over 10 code execution paths any day. Oh well. Your closing statement is absolutely correct tho. |
|
|