> -----Original Message----- > From: David P. Donahue [mailto:ddonahue@xxxxxxxxxxx] > Sent: Montag, 13. März 2006 16:21 > To: users@xxxxxxxxxxxxxxxx > Subject: Re: [users@httpd] SSL And Virtual Hosts > > > The web (and this mailing list) is replete on subject of > SSL and NBVHs. Most recent: > http://marc.theaimsgroup.com/?l=apache-httpd-users&m=114137608 115220&w=2 > > > > Or search the archives and/or google for "SSL NBVH". Not to > mention the docs: > http://httpd.apache.org/docs/2.2/ssl/ssl_faq.html#vhosts2 > > Hmm. It would seem that I'm SOL for running true SSL then? > My router > (until I can budget a more professional one) can only forward so many > ports making using other ports not a scalable solution, and > I'm NATing > behind a single IP so there's no way I can just assign more IPs to my > web server. > > I suppose for now I can forgo the authentication and just settle for > encryption, leaving my other domains with warning messages that the > certificate is for the default domain. It's not pretty, but > it's still > better than no encryption at all, right? For most serious applications of SSL, not really... Imagine you went to buy a book at Amazon and when you clicked on "checkout", you got a warning saying, "we're having a problem with our server and so you might get a browser warning about site name not matching certificate. Don't worry, just carry on and type in your credit card number anyway..." - would you? I guess if you have a limited application where the server holds the confidential data and the clients are just browsing it and there's no conceivable risk of anyone impersonating the server to serve up false data, then maybe it would be enough. But if the clients have anything confidential to submit, you really need authentication as much as encryption - put it another way, if you send your money off in an armoured car, you'd better make sure the driver really goes to the bank. Rgds, Owen Boyle Disclaimer: Any disclaimer attached to this message may be ignored. > > My searches aren't turning up any more creative solutions to this > problem. But if anyone has any I'd love to hear them. > > > Regards, > David P. Donahue > ddonahue@xxxxxxxxxxx > http://www.cyber0ne.com > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP > Server Project. > See <URL:http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > > This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please notify the sender urgently and then immediately delete the message and any copies of it from your system. Please also immediately destroy any hardcopies of the message. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. The sender's company reserves the right to monitor all e-mail communications through their networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of the sender's company. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|