Compatible with Mac OS X Server 10.6?

Bradley Giesbrecht pixilla at macports.org
Mon May 2 07:22:28 PDT 2011


On May 1, 2011, at 7:02 AM, René Fournier wrote:

>> You may be better off just rebuild the mod_ssl module for Apple's apache rather than rebuilding all of apache... you'll probably run out of duct tape and crazy glue.
> 
> OK, that's good to know. My only issue is SSL, since Apache is not a security risk at this point. Now, the thing is, I did compile from source the latest version of OpenSSL (1.0.0d)... I did that a couple days ago, and I thought that that was enough. I added the new binary to the PATH (/usr/local/ssl/bin)... But then I checked Apache/PHP and noticed they still were reporting the old version. 
> 
> So I guess my first question is, do I need to simply configure Apache somewhere to use the newer OpenSSL now installed?
> 
> - or -
> 
> Can I simply build mod_ssl for Apache and somehow hook that up while continuing to enjoy the benefits of Apple's magical Server Admin and other web-related services?
> 
> I see mod_ssl in httpd.conf (LoadModule ssl_module libexec/apache2/mod_ssl.so), is that what needs to be updated as well? 
> 
> If so, can anyone recommend a good walkthrough for compiling a newer mod_ssl based on the latest source?

I dont' know of a walk through but I would "sudo port install openssl <other modules I load that build use openssl>" and then Server Admn change the paths for these modules to the MacPorts location. To find them use "port contents <port name>". I don't recall exactly where in Server Admin you configure Apache modules but I remember it being relatively easy to find.



Regards,
Bradley Giesbrecht (pixilla)




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20110502/828720f5/attachment.html>


More information about the macports-users mailing list