#1983 move the sudo library outside libdir
Closed: wontfix 4 years ago by pbrezina. Opened 10 years ago by jhrozek.

For historical reasons the libsss_sudo library is packaged in libdir and that's also where the sudo binary expects it and dlopens it from.

But it's wrong from packaging perspective as the library cannot be linked with. We should move it to the same location as libsss_autofs. This change would require careful coordination with sudo at packaging level to make sure sudo'd dlopen path is changed as well.


Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.12 beta
rhbz: => 0

The fix in SSSD involves changing the default value of where we install the sudo module from /usr/lib to whatever appmodpath was set to.

The second part of the fix would be to change the default value of where the sudo plugin looks for the module. They seem to have an option called --with-sssd-lib as well.

owner: somebody => mmsrubar

Fields changed

mark: => 0

Fields changed

patch: 0 => 1

Fields changed

milestone: SSSD 1.13 beta => SSSD 1.13 backlog
sensitive: => 0

Fields changed

blockedby: => #2919

This depends on refactoring the sudo protocol first, which is a 1.14 beta task.

milestone: SSSD 1.13 backlog => SSSD 1.14 beta

This didn't happen in the 1.14 milestone again, but since it's "only" a packaging violation, it's not terribly critical.

milestone: SSSD 1.14 beta => SSSD 1.15 beta

Metadata Update from @jhrozek:
- Issue assigned to mmsrubar
- Issue marked as depending on: #2919
- Issue set to the milestone: SSSD Future releases (no date set yet)

7 years ago

Metadata Update from @thalman:
- Custom field blocking adjusted to 2919
- Custom field design_review reset (from 0)
- Custom field mark reset (from 0)
- Custom field patch adjusted to on (was: 1)
- Custom field review reset (from 0)
- Custom field sensitive reset (from 0)
- Custom field testsupdated reset (from 0)
- Issue close_status updated to: None
- Issue tagged with: Canditate to close

4 years ago

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

Metadata Update from @pbrezina:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

4 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/3025

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.

Metadata