#2855 Move libsss_sudo.so outside sssd-common
Closed: Fixed None Opened 6 years ago by adelton.

In an effort to move SSSD (the daemon) to a container and leave just the minimal bits on the host (for Atomic), I came across /usr/lib64/libsss_sudo.so which is in sssd-common (5.6 MB worth of dependencies) while other client libraries are in sssd-client (336 kB).

If it's technically possible, it'd be nice if libsss_sudo.so could be in sssd-client.

Jakub indicates it should be doable but notes that multilib has to be preserved.

Packages in sssd-client should be used by multilib applications e.g. libnss_sss.so can be indirectly "dlopened" by 64 bit applications and 32 bit application.
(32-bit web browser; ordinary 64bit applications ...)

But /usr/lib64/libsss_sudo.so will be used only by /usr/bin/sudo. If libsss_sudo.so was part of sssd-client then 32 bit version would never be used on 64 bit machine.

summary: Move libsss_sudo.so to sssd-client => Move libsss_sudo.so outside sssd-common

Yes, but that's not what I meant. I just meant if we move the library to client subpackage, then we must account for people installing both architectures, so the libsss_sudo location must not conflict between 32 and 64bit packages, especially if we move libsss_sudo out of libdir (we should).

Unless there is a project that needs this split sooner, I would target 1.14 alpha

Fields changed

rhbz: => todo

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.14 alpha

Replying to [comment:6 jhrozek]:

For planning purposes, what's the ETA on SSSD 1.14 alpha?

Replying to [comment:7 mmcgrath]:

Replying to [comment:6 jhrozek]:

For planning purposes, what's the ETA on SSSD 1.14 alpha?

Fedora 24/RHEL-7.3

As I said earlier, if you need us to do this change sooner, please just shout. It's also mostly a planning issue in our end.

Bumping the priority, this is important for container integration (and also not hard to fix, we should just do it..)

priority: major => critical

Fields changed

owner: somebody => lslebodn
patch: 0 => 1
status: new => assigned


resolution: => fixed
status: assigned => closed

Fields changed

rhbz: todo => 0

Metadata Update from @adelton:
- Issue assigned to lslebodn
- Issue set to the milestone: SSSD 1.14 alpha

5 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/3896

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.