Hi All,
We have a SQL Server 2000 setup with a Certificate for
Server Side Encryption and this works fine with ADO
connections from a C++ desktop app. Connects fine and we
have verified encryption with MS Network Monitor. Another
C++ desktop app built with DBLIB will not connect and
dbopen() quietly fails. I know MS states that DBLIB is
not being "extended" but I believe that it is still
classified as "supported".
Are thre any fundamental reasons why DBLIB doesn't seem to
work with SSL or am I just doing something wrong?
Thanks in advance,
DougHi Doug,
Unfortunately, that is a bug with dblib. I filed it sometime ago and it
has not been fixed.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Hi Kevin,
Thanks for the reply... albeit bad news :-) I know that
you can't commit, but in light of the "not extending"
status of dblib, got any idea what the chances might be of
the bug being fixed? I really, really, really promise
that I won't try to hold you to it :-))
Thanks again,
Doug
>--Original Message--
>Hi Doug,
> Unfortunately, that is a bug with dblib. I filed it
sometime ago and it
>has not been fixed.
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
>
>.
>|||You'd have to open up a case with a SQL Support Engineer to get the ball
rolling. You'll also need a Strong Business case, why you need it fixed.
The bug number is 94129, opened by me. Since it is a bug, you shouldn't be
charged for opening the case.
Hope this helps,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
Tuesday, February 14, 2012
DBLIB with SSL
Labels:
adoconnections,
app,
certificate,
database,
dblib,
desktop,
encryption,
forserver,
microsoft,
mysql,
oracle,
server,
setup,
sql,
ssl
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment