> Which seems to suggest that I'd need to have installed the apache > port /usr/ports/www/apache13-modssl instead of the package apache-1.3.37_3.
Right. > So, do I need to remove the apache-1.3.37_3 package (presumably with > pkg_delete, as I think that's the cleanest way, please correct me if I'm You use the same/reverse way to remove that you use to install. > wrong), and re-install from the apache13-modssl port, or is there in > fact some way to just get mod_ssl and add to my existing Apache The you install apache-modssl from the ports. Of course you can install mod-ssl from the source by hand. > configuration? If both options are possible, is one better than the > other? I'd prefer not to have to re-do my apache install, but if > there's some compelling reason I should, I'm interested in knowing it. You would have to modify the httpd.conf to activate SSL anyway. Have you a lot of things in the config yet? > Also, when I've got it, I want users to have the option to use it, > not be forced to (tinkering with a Squirrelmail webmail server here), so > any information on that would be more than welcome. Any reason why you don't want to force your user to go SSL. They will be exchanging password over the network, better it is crypted, don't you think? If it is a matter of not purchasing a certificate, you can put up a page on the way to install the certificate once for all so the users are not requested again to accept the certificate. Usual configuration of Apache normally allows you to set-up two servers, one on port 80 that is not crypted and one on port 443 that is using SSL. Both services can share the same web pages, giving acces both with and without SSL. Bests, olivier _______________________________________________ email@example.com mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"