Re: [cobalt-users] HELP! RaQ3 Problems

[Dennis <dkc@xxxxxxxxxxxxx>]

Hello Liz B-

We host all are domains under name based hosting and have had no
problems allowing users to access our secure server. What we did is went
to thawte and got a cert called 'secure.ourdomain.com'. Our users are of
course going to have to use our domain with it, but we give them access
to it with the following:

1. Created a directory called ssl in /home/sites
2. Made the document root of the secure server /home/sites/ssl Make sure
the
you change the document root at the end of the httpsd.conf file that is
between the <VirtualHost> directives. The conf file is located at
/etc/httpd/conf

Now you want to be able to let your user access the secure server via
their
website. Lets say it is site5
3. cd /home/sites/ssl
4. ln -s /home/sites/site5/web /home/sites/ssl/site5
*For the second path you can name "site5" anything you want. Say the
domain is
test.com so you make it /home/sites/ssl/test

Now when you go to https://secure.domain.com/test/ it will allow you to
call
any file up in secure mode that is in the site5's web directory.

Also "chmod o-r ssl" so that if someone goes to your your secure server
without putting in a directory they are not allowed to
see the directory structure of the ssl directory.

We set it up this way so that only sites that we create the links for
are
allowed to access the secure server.

Works great for us. Hope it helps.

    -Dennis

"Liz B." wrote:

> Any RaQ3 users out there?
>
> I have this strange feeling that the following two questions
> are going to be very popular (or should I say "unpopular")
> issues with new RaQ3 users since it's apparent Cobalt
> neglected to include these features in their version of
> RedHat v6.0.
>
> 1) I'm utilizing the name-based IPs features for virtual
> sites, but I need to be able to allow my virtual sites to
> use my current SSL certificate.  How can I get this to work
> without having to assign each virtual site their own IP
> address?   Doing otherwise would be a big waste of IPs, plus
> an unncessary added cost since additional IPs would have to
> be purchased.  I would prefer not to modify the httpd.conf
> file, or other files that the server management interface
> uses, because any changes to this file will be overwritten
> once I add new virtual sites.  I'm guessing this is somewhat
> the same senario for all of the RaQ2 users.  Or possibly, is
> there a third-party software available that would accomplish
> the same task for ssl cerficiate sharing in a named-based
> environment?
>
> 2) How do I setup alias domains (ie.
> somename.domain_name.com) through the server management
> interface?  Or is there some other file I can manually edit
> that won't affect the server management's operations??  The
> RaQ3 complains when I put "somename.", other than "www.", in
> the HOST section while attempting to add a new virtual site.
>
> Thanks in advance!
>
> ______________________________________________
> 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