SSL Backflip

[bobsomebody]

I have been picking through google trying to find out how to set up a decent SSL system that will work for my server.

The best solution I have come up with is using a single certificate on one domain and allowing users to "share" that users space. Unfortunately I dont know enough about the configs to pull it off.

Basically this is what would need to happen:

1. All users on the system will have a symbolic link from private_html to secured.domain.com/username_private_html

2. All files in secure.domain.com/username_private_html should count against the respective users quota, while the secure domain would have unlimited quotas.

3. All existing user files in private_html should be moved to the new locations.

4. I would also need a way to skip this if a user decides to purchase an IP.

5. The secure.domain.com/username_private_html should also be chown'ed to username:username

We have iPannel and DA set up on the server and not much else besides centova cast.

My idea for acheaving this is to basically hit a shell script upon creating users who have packages called "special package". I am not entirely sure on how the quotas work, and I am also concerned with updates.

I wanted to kinda start a discussion about how to do this because it seems like it would be a great way to get around some of the issues with ssl.

I read this thread and I can only assume it is possible but they dont say how:
http://hostpc.com/community/archive/index.php/t-2893.html

 

[nobaloney]

You've made one important mistake in your analysis:

If you link private_html to another directory it's still looking for a secure certificate for the original domain; apache doesn't even know it's looking at a directory in another site.

Another important issue is that you can't buy a Certificate for *.com, which you'd have to do to cover all .com domains on your server.

Instead, create for your server a location for using a shared Certificate for one domain, for example:

secure.example.com

where example.com is replaced by the domain name you're using.

Then set a private IP# for secure.example.com, and buy and install a Certificate for secure.example.com.

Each site using the shared certificate will have to link to:

https://secure.example.com/directory

where directory is the name of the directory for that site (you can use either the domain name (without the www. prefix) or the username for the directory name.

Then on the site for secure.example.com set up subdirectories for each of these, in that domain's private_html directory. Then set up an ftp account for secure.example.com for each such directory, with access to only that directory, and give your user(s) access information for that FTP account.

Jeff