Bug 1640722

Summary: mod_md is missing in httpd24-httpd
Product: Red Hat Software Collections Reporter: Luboš Uhliarik <luhliari>
Component: httpdAssignee: Luboš Uhliarik <luhliari>
Status: CLOSED ERRATA QA Contact: Branislav Náter <bnater>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: httpd24CC: bnater, jorton, lkuprova
Target Milestone: alphaKeywords: FutureFeature
Target Release: 3.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Release Note
Doc Text:
This update adds the mod_md module to the httpd24 Software Collection. This module enables managing domains across virtual hosts and certificate provisioning using the Automatic Certificate Management Environment (ACME) protocol. The mod_md module is available only for Red Hat Enterprise Linux 7.
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-13 08:37:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Luboš Uhliarik 2018-10-18 15:11:27 UTC
Description of problem:
mod_md is missing in httpd24-httpd. It's a pretty important feature and we want to include it in httpd24-httpd

Version-Release number of selected component (if applicable):
httpd24-httpd-2.4.34-3.el7

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:

checking for pkg-config along :/opt/rh/httpd24/root/usr/lib64/pkgconfig:/opt/rh/httpd24/root/usr/share/pkgconfig... checking curl/curl.h usability... no
checking curl/curl.h presence... no
checking for curl/curl.h... no
checking for curl version >= 7.50... FAILED
no
configure: WARNING: libcurl not found
checking for arc4random_buf... no
checking whether to enable mod_md... no (disabled)

current libcurl version is 7.47, we need to rebase it as well. 

Expected results:


Additional info:

Comment 10 errata-xmlrpc 2018-11-13 08:37:08 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:3558