[OT] Do dylibs have to be marked as executable?
[OT] Do dylibs have to be marked as executable?
- Subject: [OT] Do dylibs have to be marked as executable?
- From: "Karan, Cem (Civ, ARL/CISD)" <email@hidden>
- Date: Thu, 4 Oct 2007 08:00:31 -0400
- Thread-topic: [OT] Do dylibs have to be marked as executable?
This is an off-topic question, but I think this group has the best
chance of answering it correctly.
I've been working on hardening a OS X machine I have (not plain Darwin)
and one of the things I've been doing is changing the permissions of
files so that they are the minimal necessary for them to work correctly.
Part of that is changing files that are marked as executable to no
longer being executable, and I ran into a peculiar problem; I don't know
if *.dylib and *.so can be safely set to not being executable. Part of
me says that it is OK because they aren't applications, but are merely
linked into applications, which are marked as executable. Another part
of me says that they are code, and so need to be executable. ` find / \!
-perm +100 -type f -name '*.dylib'` does turn up some files that are
marked as not being executable in this manner for both, but you can also
find a bunch that are executable. So, which is it? Should they be
executable or not?
Thanks,
Cem Karan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden