Re: Permissions for shared libraries in Kerberos

Ken Hornstein <[email protected]> writes:

> Oh, interesting.  So ... is this just a _packaging_ thing?

Yeah, basically.  I don't think Debian Policy has any requirement about
this, but dh_fixperms in debhelper will remove the executable bits.  The
packaging scripts for glibc add the executable bit back to libc.so.6
because it prints out useful information when exected.

% /lib/x86_64-linux-gnu/libc.so.6 
GNU C Library (Debian GLIBC 2.31-4) stable release version 2.31.
Copyright (C) 2020 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 10.2.0.
libc ABIs: UNIQUE IFUNC ABSOLUTE
For bug reporting instructions, please see:
<http://www.debian.org/Bugs/>.

> I personally have no opinion on whether or not the execute bit SHOULD be
> set in general on shared libraries; it seems like there's valid
> arguments for both sides.  My only point was that it seems like at least
> Linux systems that use RPM expect it to be there, but clearly that's not
> even a universal requirement across all Linux distributions.

Yeah, coming from a Debian background, I find that very surprising, but I
can confirm that all the shared libraries seem to be executable on Red Hat
systems, so this is a real distribution difference.

-- 
Russ Allbery ([email protected])             <https://www.eyrie.org/~eagle/>
_______________________________________________
krbdev mailing list             [email protected]
https://mailman.mit.edu/mailman/listinfo/krbdev