First impression on unpacking the Q702 test unit was the solid feel and clean, minimalist styling.
How secure is Safari?
- — 31 January, 2009 01:37
Settings and ciphers
An optional menu called Develop (which replaces the previous Debug menu option) can be added to the menu bar to speed up Web page development testing, but it also has significant global security impacts. The Develop menu allows the user to quickly open a current Web page in another installed Web browser or to change User Agent strings on the fly (to see how the change affects Web page rendering). Installed plug-ins can be viewed -- but not managed -- via an option under Safari's Help menu.
Safari is weaker than its competitors in several areas regarding digital certificates and SSL/TLS (Secure Sockets Layer/Transport Layer Security) traffic. Initially, in SSL/TLS negotiations, TLS with RSA and weak 128-bit RC4 keys are offered first and second in the cipher order. Worse, ECC (Elliptical Curve Cryptography), AES (Advanced Encryption Standard), and 256-bit keys are never offered as potential cipher choices; further, MD5 is offered first and more frequently than SHA-1, when it should be the other way around. It would seem that Apple hasn't been paying attention to crypto developments over the last few years.
Safari does warn of invalid digital certificates, but it isn't nearly as "in your face" as the other top browsers. It warns only once with a small pop-up message, whereas competitors alter the entire Web page with red or multicolored warnings. Come to think of it, maybe Safari has it right: better to display one warning than many for a single problem. But then Safari, unlike all its competitors, fails to point out Extended Validation (EV) certificates or, as Internet Explorer and IE do, to highlight the true domain name, making it more difficult to tell phishing sites from the real thing.
Hunting and phishing
When Safari was first released, Apple touted the new browser as a secure alternative to Internet Explorer. As with all Internet Explorer alternatives, Safari's lack of native support for ActiveX controls does provide users with some protection. Safari's strong anti-phishing filters are also a plus.
But security is not Safari's strong point. Unfortunately, 26 separate vulnerabilities have been announced since March 2008, one-third of which would allow complete system access. Plus, there simply isn't a lot of security granularity to Safari. Security-minded users will have to decide if Safari's poor cipher support, lack of security zones, and absence of enterprise features for mass deployment and control can be overcome by its aesthetic benefits.