Monday 20 August 2007 10:05:43 am
I have a client who wants their db to be encrypted *and* to run on https due to sensitive information. I personally think this is overkill, but I have to see what can be done if they insist. First of all, what is involved in this. I can't find a "how to" anywhere in the docs or forum, much less a mention of this. Has anyone else setup anything similar? If so how big of a performance hit should we expect going this route? Any real world numbers would be most insightful. I think that https would be enough of a performance hit in the first place, but anything that would back up my argument is great. Alternately, is there a way to have one node on https while the rest of the site has a standard setup? Any direction from someone who has traversed this road would be most helpful and appreciated. Thanks!
|