Rationale for giving .so files +x

[Mike Frysinger]

On Friday 15 June 2007, Andreas Jaeger wrote:
> Mike Frysinger <vapier@gentoo.org> writes:
> > On Thursday 14 June 2007, Serge van den Boom wrote:
> >> What's the rationale for setting the executable bit on shared object
> >> files?
> >
> > shared object codes include executable code so in order to map them with
> > execute permissions, you need the +x bit
>
> This is not needed under Linux, it works fine if you remove the +x.  The
> dynamic linker in glibc takes care of it.

the default setup vanilla setup is like this, but there are kernel patches out 
there for the security conscience which makes the +x actually respected

> But there's one exception: You can really execute on Linux libc.so, try:
> /lib/libc.so.6

that's cause that lib cheats ;)
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 827 bytes
Desc: This is a digitally signed message part.
URL: <https://sourceware.org/pipermail/binutils/attachments/20070615/966cc55c/attachment.sig>