|
|
Posted by pigeon on 06/29/05 07:36
"Erland Sommarskog" wrote:
>pigeon (DoNotEmail@dbForumz.com) writes:
>> Ok.. it looks like we can only initiate a secure transaction
>> serverside.. when we try to initiate a secure connection clientside
>> (of course serverside encrypttion has to be off).. then we get the
>SSL
>> security error.
>
>I have never worked with encryption, so I dont 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.)
>
>Ive 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
certificates 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-Discussions-connectionopen-SeCDoClientHandshake-SSL-Security-error-ftopict235551.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.dbforumz.com/eform.php?p=819787
[Back to original message]
|