Note: Cross-posted from my question at ServerFault: http://serverfault.com/questions/176595/sql-server-2008-r2-express-wildcard-ssl-certificate
(Not trying to be a jerk, just think I might get a better response here.)
Wildcard certificates (for example, *.example.com) simply did not work in SQL Server 2008 or lower. But
Encrypting Connections to SQL Server on MSDN states, plain as day, that
SQL Server 2008 R2 supports wildcards certificates.
Excellent. So I set up SQL Server 2008 R2 Express on a machine, and I configure the
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQLServer\SuperSocketNetLib\Certificate entry to the thumbprint of my wildcard SSL certificate (because in five years of dealing with SQL server, I have never gotten that #$@#
dialog in Sql Server Configuration to display any certificates).
The SQL Server log then tells me that this went over quite well:
2010-08-31 11:46:04.04 Server The certificate [Cert Hash(sha1) "5DDD9E51B30E0CA6CE3656AE54EC6D0B8B75904A"] was successfully loaded for encryption.
Unfortunately, if I attempt to use Microsoft SQL Server Management Studio (the 2008 R2 version) or the Sql* classes provided in the .NET Framework 4.0, I always receive the following exception:
A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL
View Complete Post