Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#56593 - [libmicrohttpd] 0.9.57 may be build accidentally without HTTPS

Attached to Project: Community Packages
Opened by Evgeny Grin (Karlson2k) - Tuesday, 05 December 2017, 14:51 GMT
Last edited by Christian Hesse (eworm) - Tuesday, 05 December 2017, 21:52 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

'configure' parameters in PKGBUILD for libmicrohttpd do not enforce HTTPS support.
If something goes wrong during configure (failed to detect GnuTLS), libmicrohttpd build may succeed, but will be without HTTPS support.
With '--enable-https' package will be always built with HTTPS support (otherwise build will fail).

Patch is attached.
   0004-libmicrohttpd-enforce-ht... (0.9 KiB)
This task depends upon

Closed by  Christian Hesse (eworm)
Tuesday, 05 December 2017, 21:52 GMT
Reason for closing:  Fixed
Additional comments about closing:  in svn trunk
Comment by Doug Newgard (Scimmia) - Tuesday, 05 December 2017, 16:13 GMT
"If something goes wrong"
...such as?
Comment by Evgeny Grin (Karlson2k) - Tuesday, 05 December 2017, 17:47 GMT
'configure' for some reason will unable to detect GnuTLS.
In such case, configure will generation configuration without HTTPS support and it will be successfully built and packaged, however package will be incorrect (without HTTPS support). That was happen with Fedora and it takes too long to trace source of problems on failed applications as everything reported success.

This patch will enforce 'configure' to fail if GnuTLS is not detected.
Comment by Eli Schwartz (eschwartz) - Tuesday, 05 December 2017, 17:48 GMT
Given that gnutls is a dependency enforced in the PKGBUILD, it will always autodetect gnutls. That being said, automagic dependencies are kind of ugly. Maybe the solution is that upstream should require explicitly enabling all desired features (or have autodetection failure be a fatal configuration error). :p
Comment by Evgeny Grin (Karlson2k) - Tuesday, 05 December 2017, 17:58 GMT
The one of the main advantages of MHD is very small size, which is suitable to embedded systems.
We do not want to promote dependency of external library as requirement. Moreover, libmicrohttpd is very portable and it is possible to build it even on platforms without support for GnuTLS.
Currently MHD is designed to be very easy for build and to automatically use all available resources, i.e. require minimal manual work. That is perfectly fits novice users and untested platforms.
For any special builds, like build for packaging, all features could be easily fine-tuned by configure parameters.

As this PKGBUILD describes building of libmicrohttpd with HTTPS, correct 'configure' parameters must include '--enable-https'.

Loading...