Re: [cobalt-users] SSL is driving me crazy

[John Bush <jbush@xxxxxxxxxxxxxxx>]

you need to make symbolic links from your main site to that of other
sites:

For instance, your site is at /home/sites/www.maindomain.com/web
Theirsite is at /home/sites/www.theirsite.com/web

Telnet to your server and type:

ln -s /home/sites/www.theirsite.com/web
/home/sites/www.maindomain.com/web/theirsite

That will make a symbolic link in your main site's web space to the
other virtual site.

Then to call theirsite securely, you would access:
https://www.maindomain.com/theirsite/filename.html

This way you won't have to copy any files or create any more users.
You may have to do some ownership and group fiddling to get cgi scripts
to work, that is my personal task for tomorrow.

Liz wrote:

> I tired doing something similar to
> "secure.yoursite.com/theirsite1" but no such luck. I'm not
> using "secure.domain.com"...just a regular "www.domain.com"
> as my SSL domain name which has a certificate.  Maybe that's
> why I'm having problems?
>
> It seems the only other option I'm stuck with is to create a
> user for each site where the URL would be...
> https://www.domain.com/~user/
> I'm not crazy about doing this at all since I would prefer
> it if all user files remained within their own directory
> structure.
>
> I was informed today that Cobalt didn't make a SSL patch for
> the RaQ3 as they did for the RaQ2.  Until that's available
> the following isn't suppose to work
> https://www.domain.com/site#/
> Please share how you got your's working! :)
>
> ------Original Message------
> From: Jeff Lasman <jblists@xxxxxxxxxxxxx>
> To: cobalt-users@xxxxxxxxxxxxxxx
> Sent: January 21, 2000 9:00:10 PM GMT
> Subject: Re: [cobalt-users] SSL is driving me crazy
>
> At 10:43 AM 1/21/00  Liz wrote:
> >I'm seriously lost on this SSL stuff and am hoping someone
> >in this group can help answer the following...
> >
> >What the best way to setup the RaQ3 so each virtual site
> can
> >share one common ssl certificate?
>
> There's only one "real" way to do this without each virtual
> site customer
> getting a warning each time they  enter the site:
>
> secure.yoursite.com/theirsite1
> secure.yoursite.com/theirsite2
>
> Both Verisign and Thawte will tell you this is a violation
> of their
> license.  However, they'll also tell you (under duress, but
> they will) that
> everyone does it.
>
> So, yoursite.com gets the stand-alone IP# and the
> certificate.  The rest is
> all subdirectories.
>
> >Is it required that each virtual site must have it's own IP
> >address in order to share, or can it work with name-based
> >hosting?
>
> Theirsite1.com and theirsite2.com, etc., can have name-based
> hosting.  Secure.yoursite.com needs its own IP#.
>
> Jeff
>
> --
> Jeff Lasman, nobaloney.net
> <jblists@xxxxxxxxxxxxx>
> <www.nobaloney.net>, <www.mailtraqna.com>,
> <www.email-lists.com>
>
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> http://list.cobalt.com/mailman/listinfo/cobalt-users
>
> ______________________________________________
> FREE Personalized Email at Mail.com
> Sign up at http://www.mail.com?sr=mc.mk.mcm.tag001
>
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> http://list.cobalt.com/mailman/listinfo/cobalt-users

--
John Bush
Systems Administrator
Apex Web Technologies
http://apexhosting.com
Toll Free (877) 377-APEX