Home > Archive > Microsoft SQL Server forum > June 2005 > Re: Re: Re: connectionopen (SeCDoClientHandshake().]SSL Security









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Re: Re: Re: connectionopen (SeCDoClientHandshake().]SSL Security
pigeon

2005-06-29, 3:23 am

"Erland Sommarskog" wrote:
>pigeon (DoNotEmail@dbForumz
.com) writes:
>SSL
>
>I have never worked with encryption, so I don’t know. I did
>actually
>play with it recently for a test script, and I think I arrived at a
>similar conclusion. But I did not even have a certificate. (What I
>wanted
>to test was whether a module that I have handles the Encyption option
>correctly, but I had to leave that out.)
>
>I’ve relayed your posts to our internal MVP forum, to see if
>anywhere there
>knows about this.
>


Great thanks!

I figured it out.. and I think it is just a bug

the solution to my problem was to
create a key in the registry named "certificate" and put my
certificate’s thumbprint in the key.

This is somewhat normal..

but the other wierd thing is...

In order to have encrypted or unencrypted traffic, I have to tell SQL
to ’force encryption’ via creating a certificate named "encrypt" and
putting this value to 1

w2k
ms sql 2000 sp4

--
Posted using the http://www.dbforumz.com interface, at author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.dbforumz.com/General-Dis...pict235551.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.dbforumz.com/eform.php?p=819787
Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2008 droptable.com