February 27, 2004 at 3:14 pm
Hello All ...
I am trying understand how SQL Server works with SSL. The project I am working on looks as though it will require, beyond SQL authentication and authorization, an encrypted connection between our SQL server (stand alone) and user machines - ODBC-compliant databases - spread out over a very wide geographical location.
Okay, so what I want to do is to have our SQL Server enforce encryption, and have found data online that describes how you do that. But, I am not clear on what is required on the user side. What do they need to do? I know they need the private key to decrypt what comes from our SQL Server and to encrypt what they send to us, but that is where I get all balled up. Do they need a certificate too? I am used to seeing SSL arrangements between web servers and browsers. There, you get the certificate set up on the web server and the browser is smart enough to take care of the user side. In this case, I get confused trying to picture what needs to occur at the user's database.
Does anyone know how this works? Can someone shed any light on this? (in as simple of terms as is possible).
Thanks,
Adria
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply