|
|
No need to worry about instances
This post could easily lead to people shunning nib files unnecessarily. A nib file never contains compiled code. It only contains references and instructions for unpacking. Even if you add a nib file containing instances of malicious classes, it cannot create these objects unless you also add a framework containing the compiled code. It will merely result in an error message being written to the console. Yes, a nasty nib can mess up an application's operation, but unless the application was already capable of destroying data, the nib can't do any serious damage. As an example, if you had a program designed to delete files based on search criteria, putting in a malicious nib could do things like deleting all your files, but putting a malicious nib into, say, iColumns, can't do any damage. In case you're wondering, I can, and do, program for Cocoa. I have one freeware application on the web in beta form, EasyLookup. It's a graphical Lookup/Whois/Finger client (not just a shell for the command-line tools). You can get it (along with source code) from http://melba.vu.edu.au/~s3530650/. Vasantha Crabb |
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.09 seconds |
|