1 |
Joerg Schilling schrieb am 26.04.2013 19:07: |
2 |
> Daniel Pielmeier <billie@g.o> wrote: |
3 |
> |
4 |
>>> without making them suid-root. |
5 |
>>> |
6 |
>>> This works with cdrtools-3.01a14 or later. Check |
7 |
>>> |
8 |
>>> ftp://ftp.berlios.de/pub/cdrecord/alpha/ |
9 |
> |
10 |
>> Thanks Jörg, |
11 |
>> |
12 |
>> I have read the release notes for alpha14 and prepared an ebuild |
13 |
>> which automatically applies the required capabilities if the filecaps |
14 |
>> USE flag is set. |
15 |
>> |
16 |
>> Is there any chance to make this a configurable option, so it is |
17 |
>> possible to disable file capabilities even if libcap is installed? |
18 |
> |
19 |
> If you install cdrecord/cdda2wav/readcd suid-root instead of applying the |
20 |
> facps privileges, cdrtools will automatically behave as before. Is this |
21 |
> sufficient? |
22 |
> |
23 |
> Note that if cdrtools was compiled on a machine with libcap installed, it needs |
24 |
> libcap to run. |
25 |
> |
26 |
> Jörg |
27 |
> |
28 |
|
29 |
Actually it is the linkage against libcap what I am concerned of. |
30 |
|
31 |
Imagine the following scenario. Libcap is not present on the system. |
32 |
Then package X which requires libcap is installed and the package |
33 |
manager who knows this installs libcap as a dependency. Then package Y |
34 |
is installed which unconditionally links against libcap. The package |
35 |
manager is unaware of this and does not know about the dependency. Now |
36 |
package X is uninstalled and the package manager removes libcap because |
37 |
he thinks nothing on the system needs it anymore. Now package Y will |
38 |
stop working because libcap is not there anymore. If it is possible to |
39 |
conditionally link against libcap such issues could be avoided. Libcap |
40 |
will not be uninstalled if the dependency is known. Additionally it is |
41 |
possible to have libcap installed and not link cdrtools against it. |
42 |
|
43 |
-- |
44 |
Regards |
45 |
Daniel |