Bug#301155: Apache2 IfDefine SSL just bit me on a Sarge to Etch upgrade
I just upgraded a system from Sarge to Etch and the SSL stuff didn't
come up. I didn't realize it hadn't at first because port 80 was working
fine.
It seems that SSL is not defined, because the directive in the IfDefine
SSL blocks in ports.conf and sites-enabled/default, which are
essentially the same as the day they were put there by the Sarge apache2
package, were not executed.
In March of 2005 Adam wrote to this bug that SSL should be defined every
time. The changelog entry of 28 Sep 2004 for apache2 (2.0.52-1) in
/usr/share/docs/apache2-mpm-prefork backs this up, saying that startssl
should be used consistently in the init script.
My Etch apache2 initscript doesn't have the text startssl in it. If SSL
is still being defined every time, it seems to be undefined by the time
it hits the ports.conf and sites-enabled/default conf snippets. If it is
no longer used, I am unable to locate the README or changelog noting this.
I don't mean to AOL, but Claus' question is unanswered in the bug
report. What is the correct (most forward compatible) way to enable and
check for SSL support in the Debian apache2 package?
--
Jacob
Reply to: