In any case, browser clients will display a warning message when any hostname other than the one used to create the cert is used to access the HTTPS server.
Warning is ok... I used to get warnings before I created a cert with webmail.hserus.net on that box.
But since I patched apache to use ipv6 what happened is that I get a 403 forbidden.
Hmm... is it that SSL doesn't work when bound to two different IPs?
webmail.hserus.net has an ipv4 and an ipv6 IP.
So maybe I'll make secure.hserus.net with just an ipv6 IP, and redirect webmail.hserus.net to secure.hserus.net
Worth a try.
srs
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ linux-india-help mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/linux-india-help
