|
|
Resource Forks!!
It seems to me that there are several problems that all go back to one central issue: resource forks! Mac OS X uses the file extension to determine which app to use if a file does not have a resource fork. If a file has a resource fork, the application associated with the file can be different from the application associated with the extension. You set this in the Finder Get Info menu by changing the Open with option. Usually this is not an issue because files that arrive by download, E-mail, or other means come without resource forks. There are some exceptions, though. Resource forks can be included in ZIP archives, and BOMArchiveHelper.app reconstructs them for the extracted files. Mail.app can handle resource forks as well. I am sure there are others, too. This is a huge problem.
Resource Forks!!
Exactly - anything else but changing from HFS to a proper POSIX compliant Unix file system (without resource forks) will be a short term fix till the next exploit comes along - this was only a POC - once it is realised how easy it is to exploit Macs the fun will begin. It's time to say goodbye to Classic and to take the OS that Next developed and match it to a proper secure Unix file system where this type of nonsense just wouldn't happen. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.23 seconds |
|