[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#987156: marked as done (mod_ssl depends on mod_setenvif while it does not)

Your message dated Wed, 7 May 2025 17:24:20 +0200
with message-id <1531e3d5-c058-4f30-ab98-68673d9cab40@dietpi.com>
and subject line Re: Bug#987156: Info received (Bug#987156: Info received (Bug#987156: Acknowledgement (mod_ssl depends on mod_setenvif while it does not)))
has caused the Debian Bug report #987156,
regarding mod_ssl depends on mod_setenvif while it does not
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
987156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987156
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apache2
Version: 2.4.46-4
When enabling mod_ssl via "a2enmod ssl" while mod_setenvif is disabled, it becomes apparent that mod_ssl depends on mod_setenvif. I checked the configuration file /etc/apache2/mods-available/ssl.conf, but it actually does not use any mod_setenvif directive. I disabled mod_setenvif effectively by emptying setenvif.load and setenvif.conf manually on two servers, and none shows any issues for months of 24/7 use.
Hence I believe that this module dependency might come from some previous use of setenvif directives in the default mod_ssl config, which have been removed meanwhile, rendering this dependency as obsolete.
I'm not sure how those dependencies are defined and whether hence it is an upstream issue or a distro package issue. In case I'll report it upstream as well. 

Best regards,

Micha

--- End Message ---
--- Begin Message --- 
Version: 2.4.63-1
The MR has been merged, adjusting this since Trixie. It has been merged earlier, and the commit is contained in Bullseye and Bookworm branches and tags, but it has been reverted to minimise diff during Bookworm freeze. Hence using the current Trixie version as the one which closes the report.
--- End Message ---
Reply to: