: !/bin/sh

echo "Step 5: Install generated ssl files to apache conf"
cp server.key /usr/local/apache/conf/ssl.key/server.key
chmod 400 /usr/local/apache/conf/ssl.key/server.key

cp cert.cer server.crt
cp server.crt /usr/local/apache/conf/ssl.crt/server.crt
chmod 400 /usr/local/apache/conf/ssl.crt/server.crt

cp server.csr /usr/local/apache/conf/ssl.csr/server.csr
chmod 400 /usr/local/apache/conf/ssl.csr/server.csr
echo ""
exit
 

echo ""
echo "Step 6: Manually tweak /usr/local/apache/conf/httpd.conf"
cat <<MSG2
eg.
Listen xxx.xxx.xxx.xxx:443
(Note: Replace the x's with your IP or DNS name. You can listen to a different port, although 443 is standard for https.)

SSLEngine on 

--------------------------------------------------------------------------------
SSLCertificateFile /etc/httpd/ssl.crt/server.crt
SSLCertificateKeyFile /etc/httpd/ssl.key/server.key

(Note: Of course you can select different directory locations for the .crt and .key files. Just make sure you reference the proper location where you placed them in an earlier step, and that you manage their permissions very carefully.) 

--------------------------------------------------------------------------------
Most likely some other various tweaks. For example, you might want to create a separate directory from which to serve ssl web pages. What's nice about this is that you'll never inadvertently serve a sensitive page through port 80 so long as you develop in two separate places. Perhaps /var/www/html for basic port 80 stuff, and /var/www-ssl/html for port 443 or SSL delivered pages, or under /srv/... as typical under some SuSE distros. An example from Red Hat:

<VirtualHost _default_:443>
# General setup for the virtual host; inherited from global configuration.
DocumentRoot "/var/www-ssl/html" 


Finally...
restart  apache with /etc/apache restart

test with...
curl -k https://mon2/
MSG2



exit 0