Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

Encrypt connection to SQL Server 2005 Expand / Collapse
Author
Message
Posted Friday, February 5, 2010 11:02 AM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Thursday, October 23, 2014 2:26 PM
Points: 752, Visits: 1,071
Hi,

I need to encrypt the connection that my VB 6.0 app uses to connect to SQL Server 2005.

My app connects to SQL using SQL Server authentication.

Is there a problem with this?

Thank you
Post #860688
Posted Friday, February 5, 2010 11:46 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 8:48 AM
Points: 12,923, Visits: 32,285
as i understand it, you should do this in two places;

you can make your server require encryption from everything connecting,a dnt he native client will handle it automatically:
SQL Server Configuration Manager and click properties for "SQL Native Client Configuration", if correct, you should be able to see two flags, one is "force client encryption", which you want to toggle to yes.


seperate from that, when you build an application with a connection string, one of the parameters is Encrypt=yes;
Driver={SQL Native Client};Server=myServerAddress;Database=myDataBase;Trusted_Connection=yes;Encrypt=yes;



Lowell

--There is no spoon, and there's no default ORDER BY in sql server either.
Actually, Common Sense is so rare, it should be considered a Superpower. --my son
Post #860733
Posted Saturday, February 6, 2010 1:46 PM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Thursday, October 23, 2014 2:26 PM
Points: 752, Visits: 1,071
But there is no problem with encrypting a connection because it uses SQL Server authentication instead of windowns authentication, correct?


Or i can only encrypt connection if they use windows authentication to connect to the server?



Thank you.
Post #861179
Posted Saturday, February 6, 2010 1:56 PM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 8:48 AM
Points: 12,923, Visits: 32,285
river1 (2/6/2010)
But there is no problem with encrypting a connection because it uses SQL Server authentication instead of windowns authentication, correct?
Or i can only encrypt connection if they use windows authentication to connect to the server?
Thank you.


the encryption is for all the packets transferred to and from SQL Server, regardless of any authentication protocols or any other settings; so it's fast and cheap to just make the server require encryption.

you cannot be selective and make only one authentication type require encryption; about hte only option might be that you could make an application always use encryption even if the server did not require encryption by default, by adding to the connection string.


Lowell

--There is no spoon, and there's no default ORDER BY in sql server either.
Actually, Common Sense is so rare, it should be considered a Superpower. --my son
Post #861181
Posted Saturday, February 6, 2010 2:26 PM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Yesterday @ 4:18 PM
Points: 17,947, Visits: 15,940
No problem with encrypting communications to the server.

Another method is to establish an ssl certificate on both the client and the server.




Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw
Post #861191
Posted Monday, February 8, 2010 3:14 AM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Thursday, October 23, 2014 2:26 PM
Points: 752, Visits: 1,071
Hi,

I i'm very confused...
Are there any differences between Encrypting a connection to SQL Server and using SSL?

I thought the two where the same.

Can anyone explain to me the differences betweeen the two? can you give me a good link this?

Thank you very much
Post #861517
Posted Monday, February 8, 2010 5:29 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 8:48 AM
Points: 12,923, Visits: 32,285
SSL is an https connection for a web page, using port 443 by default. in theory, i can go to your web page via https, but your web server goes to a different server for SQL data via the default of port 1443. so the data between your Web server and your SQL server is not encrypted. , but when the data is passed back to me via https SSL on the web connection, it is encrypted.

The same thing for when you connect directly to the SQL Server via SSMS or your application or whatever...the traffic passed back and forth is not encrypted.
That is the SQL specific info we were giving you, so you can easily force the traffic to and from the SQL server to be encrypted.


Lowell

--There is no spoon, and there's no default ORDER BY in sql server either.
Actually, Common Sense is so rare, it should be considered a Superpower. --my son
Post #861568
Posted Monday, February 8, 2010 5:52 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, April 28, 2014 8:38 AM
Points: 103, Visits: 215
ssl is added as an layer and is independent of sql server or https. it's just used as a component. just like if you add ssl to ftp you get sftp. or telnet -> stelnet etc.

How to enable SSL encryption for an instance of SQL Server by using Microsoft Management Console
http://support.microsoft.com/kb/316898

Post #861582
Posted Monday, February 8, 2010 6:20 AM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Thursday, October 23, 2014 2:26 PM
Points: 752, Visits: 1,071
But in my case, my apps are intranet apps made in Visual Basic. This are windows aplications they do not use the browser.

In this case, what i want is that because my VB aplication connects to SQL Server via SQL Server authentication, and because SQL Server authentication goes in plaintext by default, anyone with a sniffer or with profiler can see the passwords of the users that are hard coded inside my VB aplication.

what i want is that this informations can not be seen by sniffers of by profiler so i think i want to encrypt it.


What type of procedure would you advice?


Thank you.

Post #861597
Posted Monday, February 8, 2010 6:29 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 8:48 AM
Points: 12,923, Visits: 32,285
yeah, encryption can be confusing; I didn't know SSL was an added layer; so I learned something today; (as usual here on SSC) Thanks Eduard!

river by changing that flag i mentioned before, "Force Protocol Encryption" to yes, you will achieve what you were after; traffic going to and from your SQL server will be encrypted. so your application will be more secure.

you can grab a scanner and see if you are not sure, or of course there's lots more information on MS or via google if you need deeper details to document how much more secure it will be. I know it's one thing to "say" it's more secure, and another to be able to show the chain of command.


Lowell

--There is no spoon, and there's no default ORDER BY in sql server either.
Actually, Common Sense is so rare, it should be considered a Superpower. --my son
Post #861604
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse