Re: SSSD Maintained?

Thank you all for volunteering. I can try to help out as well with any of
the programming/integration issues, but would need some hand-holding with
regards to packaging. (To date myself, the last time I built a Debian
package was on Woody, and I seem to recall the process involved running
./debian/rules by hand).

How do we get some of these outstanding CVEs cleared?

R/Eric

On Mon, Aug 3, 2026, 4:56 AM Simon Richter <[email protected]> wrote:

> Hi,
>
> On 8/3/26 4:09 PM, Timo Aaltonen wrote:
>
> > /usr/bin/x86_64-linux-gnu-ld.bfd: /usr/lib/x86_64-linux-gnu/
> > libkeyutils.so.1: error adding symbols: DSO missing from command line
>
> This should be fairly simple to work around.
>
> The error message means that the object being built has an undefined
> symbol that is satisfied by libkeyutils.so.1, but this library is only
> part of the link because another library depends on it, and it has not
> been explictly mentioned.
>
> If the object uses an interface from that library, it should be added as
> a proper dependency, but if it uses something like an inline function
> indirectly through another library, that library needs to be updated to
> communicate the information "consumers of this library also need to link
> against this other library" (which is possible using libtool .la files
> or CMake definitions, although for some reason Debian believes one of
> these to be a bad interface).
>
> In any case, explicitly adding the library to the link should make the
> problem go away.
>
>     Simon
>
>