One of the nicest features of Leopard is TimeMachine, the automated backup system which is built into the Leopard OS. However, there seem to be a number of issues and snags with TimeMachine.
I had a heck of a time getting TimeMachine to make it’s initial backup to a 320GB SimpleTech external USB drive. It failed 3/4 of the way through 3 times before I was successful. I noticed that any other activity on the computer while this initial backup was going would tend to hose it up. I finally set it to backup while I was away, and that seemed to do it.
I’ve heard a variety of perspectives from folks when it comes to using a mounted network drive to backup to. I have not been able to get any network drive to be seen by TimeMachine. Anyone out there have a different story?
In the meantime, here’s a list of known issues for TimeMachine, put out by Apple: Troubleshooting TimeMachine
The QuickTime vulnerability originally reported on November 15 seems to have been spotted in the wild. This is not good news.
Apple made a decision to change the firewall settings in Leopard, provoking some serious questions about the security of this new OS. This latest security issue puts a spotlight on what may become a real thorn in Apple’s side.
This from Symantec:
Originally, the flaw was disclosed on November 23, 2007 by Polish security researcher Krystian Kloskowski and since then we have seen number of exploits targeting the vulnerability being released to the public. But now the exploit is active and in the wild, meaning web surfers are in danger of being attacked. Our current analysis is also leading us to believe that there may be multiple attacks in existence. Further investigation is currently under way to confirm this.
Let me briefly explain what we have seen. The attack we have confirmed today begins with the popular IFRAME. An IFRAME code that causes the browser to make an additional request to another URL, is embedded in a porn site. Without knowledge, users visiting this site are redirected to the malicious site serving the exploit. Currently, the malware that is downloaded by the exploit is detected by Symantec as Downloader. We are still studying the attack in depth, so look out for more information at a later time.
Since a patch to correct the issue has yet to be released, we advise users to be cautious when browsing the web. For those of you seeking extra protection, we also recommend the following options:
- Run web browsers at the highest security settings possible
- Disable Apple QuickTime as a registered RTSP protocol handler.
- Filter outgoing activity over common RTSP ports, including TCP port 554 and UDP ports 6970-6999.
If you folks have Leopard, then you should be using TimeMachine to safeguard against losing files to corruption or emptied trash. But if you have not yet installed Leopard, or are simply not using TimeMachine, and you find yourself wishing you could undelete an emptied trash item, you may be in luck.
The folks at SubRosaSoft have created a solid little application called FileSalvage ($79.00) which can retrieve files even after you’ve emptied the trash. When the trash is emptied, the OS X system doesn’t actually erase the data. Instead, it informs the file management system that the space previously occupied by the file is now available for being overwritten. FileSalvage can retrieve that file as long as the data for the file has not already been overwritten with other data. This is why it’s more likely that you’ll be successful in getting your file back if you use FileSalvage as soon after the file has been trashed as possible.
You can download a trial copy of FileSalvage and check whether or not your file is recoverable, then purchase the software to implement the recovery.
Check it out: FileSalvage
The rumors of a Leoaprd update last week proved true today. Apple released 10.5.1 updates for both OS X abd OS X Server today.
The list of improvements is long: OS X 10.5.1 Update
Hopefully this update will improve TimeMachines handling my 320GB SimpleTech drive.
The casual user of Apple’s new operating system, Leopard, may not be aware that unlike in Tiger, the firewall is off by default. To turn it on, you’ll need to go to System Preferences/Security/Firewall tab.
This is a new interface which lets you specify firewall blocking by application rather than ports or services (unlike Tiger). There have been several reports that Leopard’s firewall does not behave like Tiger’s. In some cases, it appears that it is not blocking certain services indicated by the settings.
Stay tuned for ongoing information regarding Leopard’s firewall issues, including some other security issues arising from Leopard’s Screen Sharing capabilities.
