Re: Thwarting classdump, etc.
Re: Thwarting classdump, etc.
- Subject: Re: Thwarting classdump, etc.
- From: Bob Ippolito <email@hidden>
- Date: Sat, 2 Jul 2005 22:09:16 -1000
On Jul 2, 2005, at 5:41 PM, email@hidden wrote:
I'm concerned that someone who's looked into this more than I have
could get
into my code chain somehow by changing classes that my code relies
on, maybe
by modifying frameworks or something. In that case, even checking
my code
for modification won't help, since the modifications could be made
outside
of my app.
Quite true. This is why Apple don't recommend using Foundation-
based (iirc) ObjC (notably AppKit, irc) in security-conscious
programs; it's very easy, through multiple paths, for someone to
load other executable code into your app at runtime. But, even
without bundle and plugin conveniences, it's still pretty trivial
to use mach_inject or similar.
Where does Apple say that? Also, since when is it hard to load
executable code into ANY app? There's always gdb, DYLD env
variables, mach_inject, etc. which has nothing to do with Cocoa, and
none of them are hard.
-bob
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden