Ticket #1247 (closed defect: invalid)

Opened 5 years ago

Last modified 5 years ago

sssd: NSS+OpenSSL unwantedly mandatory

Reported by: dpal Owned by: jhrozek
Priority: major Milestone: NEEDS_TRIAGE
Component: SSSD Version:
Keywords: Cc:
Blocked By: Blocking:
Sensitive: Tests Updated: no
Coverity Bug: Patch Submitted: no
Red Hat Bugzilla: 802169 Design link:
Feature Milestone:
Design review: Fedora test page:
Chosen: Candidate to push out:
Release Notes:
Temp mark:


https://bugzilla.redhat.com/show_bug.cgi?id=802169 (Fedora)

Description of problem:
In sssd-1.5.x, one could choose to either use libcrypto or mozilla-nss as
crypto backend. In sssd-1.8.0, the respective PKG_CHECK_MODULE calls no longer
have an else-case, which means both libcrypto and mozilla-nss are required for
running configure, even though only one is going to be used during compilation.
(Makefile.am still has if HAVE_NSS/...)

Version-Release number of selected component (if applicable):

How reproducible:
Build sssd in an environment where Mozilla NSS is not installed.

Actual results:
checking for NSS... configure: error: Package requirements (nss) were not met:

Expected results:
Ignore NSS if not present and move on to attempt using libcrypto.

Additional info:

Change History

comment:1 Changed 5 years ago by sgallagh

  • Owner changed from somebody to jhrozek
  • tests set to 0
  • upgrade set to 0
  • Tests Updated unset

Assigning to Jakub for triage.

comment:2 Changed 5 years ago by jhrozek

  • Status changed from new to closed
  • Resolution set to invalid

This is on purpose, commit 505383ec905863bb8f4f563f694b9bf077f9002c disabled libcrypto support, removed the --with-crypto option.

I believe that if you look at your config.log, you will see a warning about uknown option --with-crypto.

Closing as notabug.

Note: See TracTickets for help on using tickets.