Re: JDBC for SQL 2000 Service Pack 4?
- From: Michael Chan <Michael Chan@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 24 Aug 2005 17:32:05 -0700
Just noticed this thread and an omission from Kamil. If the client is using
the client network utility and turns on "Force Protocol Encryption" option,
the communication between the server and that client only will be encrypted
via SSL.
"Kamil Sykora [MSFT]" wrote:
> There is no way to selectively allow some clients to connect unencrypted.
> If the setting is set on the server, all clients have to connect with SSL.
>
> Kamil Sykora
> Microsoft Developer Support - Web Data
>
> Please reply only to the newsgroups.
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> Are you secure? For information about the Strategic Technology Protection
> Program and to order your FREE Security Tool Kit, please visit
> http://www.microsoft.com/security.
>
>
>
> --------------------
> | Date: Fri, 17 Jun 2005 11:44:50 -0400
> | From: News <nooneherereally@xxxxxxxxxxx>
> | Newsgroups: microsoft.public.sqlserver.jdbcdriver
> | Subject: Re: JDBC for SQL 2000 Service Pack 4?
> |
> | Well, that would explain it. Is there a way to "force encryption
> | execept for certain clients"?
> |
> | Kamil Sykora [MSFT] wrote:
> | > The Microsof SQL Server 2000 Driver for JDBC does not support SSL
> | > encryption.
> | >
> | > There was an issue prior to Service Pack 4 for SQL Server 2000 where
> the
> | > JDBC driver was able to connect to a SQL Server database even though
> the
> | > "force protocol encryption" option was set on the server. The SQL
> Server
> | > would incorrectly allow an unencrypted connection with the JDBC driver.
> | >
> | > In Service Pack 4 for SQL Server 2000 this was fixed so that only
> clients
> | > that support SSL can connect to the server if the "force protocol
> | > encryption" option is set on the server. This will exclude the JDBC
> driver
> | > since it does not support SSL and you will receive an error on the
> client.
> | >
> | > Thanks,
> | > Kamil
> |
>
>
.
- Prev by Date: Re: Invalid operation for the current cursor position
- Next by Date: Stored Procedure error is not catched
- Previous by thread: Invalid operation for the current cursor position
- Next by thread: Stored Procedure error is not catched
- Index(es):
Relevant Pages
|
Loading