Security site knocks spots off Mac OS X Leopard firewall
Even when you turn it on it's no good
It's been a rocky week for security-conscious Mac fans. A rare appearance of a Trojan targeting Mac fans made it out onto the net and the release of Apple's much vaunted Leopard operating system was marred by security concerns about its firewall.
Reports of Leopard installs hanging at boot, behaviour compared by some to the Blue Screen of Death of Windows notoriety, didn't help either. An unsupported add-on extension for a Logitech mouse drive has emerged as the main suspect behind that stability issue.
Much has been made of the Trojan, dubbed RSPlug-A, after it was found on several porn websites. To get infected, users have to give explicit permission for the malware, which poses as a codec, to run. The firewall issue, by contrast, affects all users upgrading to Leopard - not just those hunting for free skin flicks.
Users upgrading to Leopard found the built-in firewall deactivated when they upgraded from Tiger, the previous version of Mac OS X. This removes an important defence against hacker attacks and a removes a way to prevent Mac computers infected by a worm from spreading infection. Admittedly, this is a unlikely risk, but the failing of the firewall is a surprise, given that improved security was an Apple design goal for Leopard.
A review  by Heise Security found issues with the firewall run deeper than simply been turned off by default. Even after activation the technology has a number of shortcomings.
Setting a poor example
Heise notes that, in contrast to the Windows firewall, the Leopard firewall does not include a setting to allow a distinction to be made between trusted corporate networks and riskier environments, such as Wi-Fi hotspots.
If a user selected "Block all incoming connections" the firewall reportedly blocks most ports and services, but not all. Potential hackers might be able to communicate with system services such as a time server and (possibly and more seriously) with the NetBIOS name server, according to Heise. Adding to the problems, Leopard bundles older versions of three-party open source tools known to contain security bugs.
Heise's overall verdict is damning. "The Mac OS X Leopard firewall failed every test. It is not activated by default and, even when activated, it does not behave as expected. Network connections to non-authorised services can still be established and even under the most restrictive setting, 'Block all incoming connections', it allows access to system services from the internet," it concludes
"Apple is showing here a casual attitude with regard to security questions which strongly recalls that of Microsoft four years ago," it adds.
Other researchers have criticised Leopard's firewall, albeit to a lesser extent than Heise. Security blogger Rich Mogull reckons  the firewall is a mess but he takes issue with a key Heise finding. He agrees that with "stealth mode" enabled on the firewall services show up in port scans. Crucially, however, they can’t actually be used.
In fairness it's worth pointing out that Leopard's firewall in less than a week old. Glitches and security bugs accompany every major operating system upgrade, not just those from Apple.
Windows Firewall was long present in XP, but never activated by default until Service Pack 2, after the Sasser and Nimda worm outbreaks had concentrated minds at Redmond.
Let's hope it won't take a similar such incident to spur Apple into action. ®