AFAIK with SSPI authentication, the Windows password traverses the wire to
the Domain controller if you log on to a domain--I don't know if it's
encrypted on the wire (I don't think it is).
With SQL Server (or other server-authenticated protocols) the password must
also traverse the network--the only way to prevent this is to use an
encrypted connection (and encrypt the entire TDS stream).
As I discuss in the book, another approach is to make the credentials less
important. While a given connection string password can gain access to a
data source, the objects exposed through those credentials is very
limited--focused on specific stored procedures or views. Expanded access can
be accomplished by other application-specific means.
hth
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com www.betav.com/blog/billva Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit
www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------
[quoted text, click to view] "seguso" <maurizio.colucci@gmail.com> wrote in message
news:1189531715.213545.286760@k79g2000hse.googlegroups.com...
> Hello,
>
> I have a very simple question I could find nothing about.
>
> When, in a .NET application, I connect to a database with a
> ConnectionString like "database=foo; server=220.40.231.2; uid = root;
> persist security info= false; pwd=blabla", does my root password
> travel in clear-text?
>
> AFAIU, the DB server should first send me its public key, with which I
> would encrypt my root passord. Does this really happen under the hood,
> or is my password travelling in clear?
>
> I did notice the "encrypt=true" option in the connection string, but
> it does not seem appropriate, because I don't need to encrypt all
> communication with the DB server -- just the password.
>
> Thank you very much for any reply.
>
> (I am actually using mysql with MySql Connector/Net, but I suppose
> this makes no difference. Or does it? )
>
> Maurizio
>