#1208 pam_sss requires SELinux
Closed: Fixed None Opened 12 years ago by ejona.

I just tried to build the 1.8.0beta3 on Arch Linux. When compiling, I got the following error:

src/sss_client/pam_sss.c:44:29: fatal error: selinux/selinux.h: No such file or directory

I do not have SELinux installed and thus selinux.h is correctly not found. I took a look at pam_sss and there are no conditionals around the selinux.h include and some of its symbols' usage. Is it now a requirement to have the SELinux installed? I compiled 1.6 and 1.7 without issue.


No Selinux is not required and should be optional.

Can you try the attached patch ?
I tested it by defining HAVE_SELINUX to 0 in my config.h file.

The original patch was incomplete. The linker was still trying to pull in -lselinux.

This new version correctly makes the linker optional, as well as adding another ifdef around some variables in {{{send_and_recieve()}}} that are not used if SELinux is not in play (to avoid compiler warnings).

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

Making this a 1.8.0 blocker as it will prevent non-SELinux distributions from building SSSD.

milestone: NEEDS_TRIAGE => SSSD 1.8.0 (LTM)
priority: major => blocker

Fixed by:
- 8d821f0 (master)
- 1380fad (sssd-1-8)

resolution: => fixed
status: assigned => closed

I just built from master and sssd-1-8, so your fix works for me.

Thanks for the speedy resolution. I would have tested a bit sooner, but I failed to realize I didn't have email notifications enabled.

Fields changed

rhbz: => 0

Metadata Update from @ejona:
- Issue assigned to sgallagh
- Issue set to the milestone: SSSD 1.8.0 (LTM)

7 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/2250

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