On Mar 16, 2012, at 6:53 PM, cocoa-dev-requ...@lists.apple.com wrote: > Date: Fri, 16 Mar 2012 15:53:30 -0700 > From: Jens Alfke <j...@mooseyard.com> > To: Eeyore <eey...@monsterworks.com> > Cc: cocoa-dev list <cocoa-dev@lists.apple.com> > Subject: Re: Why so many public properties all up in my grizzle? > Message-ID: <4aba472f-cdad-47f3-8544-a5538f5ac...@mooseyard.com> > Content-Type: text/plain; charset=windows-1252 > > > On Mar 16, 2012, at 2:57 PM, Eeyore wrote: > >> So simply hiding the actions in the implementation doesn't protect you from >> finding out the method's name and calling it. > > Well, sure. If you’re in the same process, there’s nothing protecting you > from malicious code. The same goes for C++ or assembly; it’s just a little > easier to find the method’s entry point in Obj-C because there’s more > metadata.
... and of course, even not in the case of hackers who are wanting to do malicious things, if any curious party can get the compiled code, they can take the time to reverse engineer it from assembly. IMO, it's generally a waste of time to try to spend too much time "hiding" things, because they're all hanging out there in the compiled code anyway :-) -gt _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
