Deprecated: Function set_magic_quotes_runtime() is deprecated in /usr/local/apache/sites/mcse.ms/htdocs/362/includes/class_core.php on line 1505

Call Stack:
    0.0001     326800   1. {main}() /usr/local/apache/sites/mcse.ms/htdocs/362/archive/index.php:0
    0.0003     327652   2. require_once('/usr/local/apache/sites/mcse.ms/htdocs/362/archive/global.php') /usr/local/apache/sites/mcse.ms/htdocs/362/archive/index.php:25
    0.0005     328940   3. require_once('/usr/local/apache/sites/mcse.ms/htdocs/362/includes/init.php') /usr/local/apache/sites/mcse.ms/htdocs/362/archive/global.php:20
    0.0013     403244   4. vB_Registry->vB_Registry() /usr/local/apache/sites/mcse.ms/htdocs/362/includes/init.php:43
    0.0013     403900   5. vB_Input_Cleaner->vB_Input_Cleaner() /usr/local/apache/sites/mcse.ms/htdocs/362/includes/class_core.php:2337

<br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in <strong>/archive/global.php</strong> on line <strong>26</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in <strong>/includes/functions.php</strong> on line <strong>3113</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in <strong>/includes/functions.php</strong> on line <strong>3265</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in <strong>/includes/functions.php</strong> on line <strong>3265</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in <strong>/includes/functions.php</strong> on line <strong>3265</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in <strong>/includes/functions.php</strong> on line <strong>3265</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in <strong>/includes/functions.php</strong> on line <strong>3265</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in <strong>/includes/functions.php</strong> on line <strong>3265</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in <strong>/includes/functions.php</strong> on line <strong>3265</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in <strong>/includes/functions.php</strong> on line <strong>3265</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in <strong>/includes/functions.php</strong> on line <strong>3265</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in <strong>/includes/functions.php</strong> on line <strong>3265</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in <strong>/includes/functions.php</strong> on line <strong>3265</strong><br /><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html dir="ltr" lang="en">
<head>
	<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
	<meta name="keywords" content="SSL Security error, vbulletin,forum,bbs,discussion,jelsoft,bulletin board" />
	<meta name="description" content="[Archive] SSL Security error SQL Server Security" />
	
	<title>SSL Security error [Archive]  - MCSE</title>
	<link rel="stylesheet" type="text/css" href="http://www.mcse.ms/archive/archive.css" />
</head>
<body>
<div class="pagebody">
<div class="archiver"><script type="text/javascript"><!--
google_ad_client = "pub-6314654110945947";
google_ad_width = 468;
google_ad_height = 15;
google_ad_format = "468x15_0ads_al";
google_ad_channel = "9315981861";
google_color_border = "2B4271";
google_color_bg = "FFFFFF";
google_color_link = "000080";
google_color_url = "008000";
google_color_text = "000000";
//--></script>
<script type="text/javascript"
  src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script>


</div>
<div id="navbar"><a href="./">MCSE</a> &gt; <a href="f-16.html">Microsoft software reviews</a> &gt; <a href="f-32.html">Microsoft SQL server reviews</a> &gt; <a href="f-97.html">SQL Server Security</a> &gt; SSL Security error</div>
<hr />
<div class="pda"><a href="?pda=1" rel="nofollow">PDA</a></div>
<p class="largefont">View Full Version : <a href="http://www.mcse.ms/showthread.php?t=559041">SSL Security error</a></p>
<hr />
<div class="ggat">
<script type="text/javascript"><!--
	google_ad_client = "pub-6314654110945947";
	google_ad_width = 728;
	google_ad_height = 90;
	google_ad_format = "728x90_as";
	google_ad_channel ="9315981861";
	google_color_border = "FFFFFF";
	google_color_bg = "FFFFFF";
	google_color_link = "0000FF";
	google_color_url = "000080";
	google_color_text = "000000";
	//--></script>
	<script type="text/javascript"
	  src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script>
</div>
<div class="post"><div class="posttop"><div class="username">Allen</div><div class="date">04-11-04, 09:51 PM</div></div><div class="posttext"><div class="ggap">something</div>I have a problem connecting to Sql server 2000 using ssl from a .net web application.  I keep getting the error message:<br />
<br />
System.Data.SqlClient.SqlException: SSL Security error<br />
<br />
<br />
<br />
Here's my config (development box):<br />
<br />
Sql server 2000 Developer's Edition on windows XP pro<br />
..net framework 1.1.4<br />
mdac 2.71.9030.0<br />
<br />
<br />
ssl configuration:<br />
versign test certificate installed through IIS.  The certificate has valid dates.  I also imported the verisign root certificate (getcacert.cer) for testing into my &quot;Trusted Root Certification Authories&quot; store.  This means when I go to IIS and hit a ssl p<br />
age, I do not get a security warning since 1. the certificate name matches name in url 2. certificate has valid dates 3. the test CA is trusted since I imported the root cert into my trusted root store.<br />
<br />
<br />
Senerios:<br />
I go into my &quot;client network utility&quot; and &quot;force protocol encryption&quot;.  I use &quot;Query Analyzer&quot; to connect to one of my databases on the sql server that has the certificates installed.  This connection is successful.  I try to connect to another sql 2000<br />
server running on another box that DOES NOT have certificates installed and the Query analyzer returns an error &quot;Encryption not Supported&quot;.  So at this point, I'm happy since it seems like the ssl connection to sql server is successful with Query Analyzer<br />
.  I try using Enterprise Manager now to connect to the ssl enabled sql server.  Successful again!  great!  finally when I try to do it from my .NET Application,  I get the dreaded &quot;SSL Security Error&quot;.  Here's the code for the .NET App:<br />
<br />
Dim con As SqlConnection = New SqlConnection(&quot;SERVER=servername.domainname.com;DATABASE=dbname;U  ID=username;PWD=pass;Encrypt=Yes&quot;)<br />
con.Open()      &lt;--------------------------exception thrown here<br />
<br />
If I remove &quot;Encrypt=Yes&quot; the connection is successful.<br />
<br />
I tried using a Oledbconnection same results.  I tried to use ODBC .net and an ODBCCOnnection. same error.<br />
<br />
Then I tried to create a System DSN with &quot;strong encryption for data&quot;.  I tested the connection in the DSN Configurator....Click on &quot;Test Data Source&quot; button.  Test Successful.  BUt when I use this DSN from my .NET application I get the same error: &quot;SSL S<br />
ecurity Error&quot;.<br />
<br />
I really would like to know if anyone has successfully used a ssl connection from a .net application?!!!???  It couldn't be the certificates!  The certificates common name is fully qualified.....servername.domainname.com<br />
The application runs on the same machine which the sql server runs, but I use the fully qualified servername in the connection string.  (beside i did try to connect from a remote machine, after installed the root test certificates as trusted...still no lu<br />
ck)<br />
On the machine that the .net application is running, I've imported the root test certificate which was installed as the server.  It is in as &quot;Trusted Root Certification Authority&quot;.  Query analyzer and Enterprise manager seem to work with the ssl encrypted<br />
connection, so how could it be the certificates?  Even on the webserver there's no security warning when I hit a https page (which means the certificates installed are trusted and valid).  My tests were mainly done with the sql server and the .net server<br />
on the same machine however I did try remote machines too with no luck.  This machine has only 1 network card and 1 website in IIS.   There's only 1 ssl certificate installed on this machine.  Anyone have similar problems?????<br />
<br />
THanks!</div></div><hr />


<div class="post"><div class="posttop"><div class="username">Allen</div><div class="date">04-11-04, 09:51 PM</div></div><div class="posttext"><div class="ggap">something</div>Ok I finally got it working, but I'm not sure what the problem is still.  When I impersonate the application to be using a domain account (which is Administrator to the machine) it works.  I tried to impersonate a local admin user and it still had the err<br />
or message.  The only way is to impersonate a domain account.<br />
<br />
----- Allen wrote: -----<br />
<br />
I have a problem connecting to Sql server 2000 using ssl from a .net web application.  I keep getting the error message:<br />
<br />
System.Data.SqlClient.SqlException: SSL Security error<br />
<br />
<br />
<br />
Here's my config (development box):<br />
<br />
Sql server 2000 Developer's Edition on windows XP pro<br />
.net framework 1.1.4<br />
mdac 2.71.9030.0<br />
<br />
<br />
ssl configuration:<br />
versign test certificate installed through IIS.  The certificate has valid dates.  I also imported the verisign root certificate (getcacert.cer) for testing into my &quot;Trusted Root Certification Authories&quot; store.  This means when I go to IIS and hit a<br />
ssl page, I do not get a security warning since 1. the certificate name matches name in url 2. certificate has valid dates 3. the test CA is trusted since I imported the root cert into my trusted root store.<br />
<br />
<br />
Senerios:<br />
I go into my &quot;client network utility&quot; and &quot;force protocol encryption&quot;.  I use &quot;Query Analyzer&quot; to connect to one of my databases on the sql server that has the certificates installed.  This connection is successful.  I try to connect to another sql 2<br />
000  server running on another box that DOES NOT have certificates installed and the Query analyzer returns an error &quot;Encryption not Supported&quot;.  So at this point, I'm happy since it seems like the ssl connection to sql server is successful with Query Ana<br />
lyzer.  I try using Enterprise Manager now to connect to the ssl enabled sql server.  Successful again!  great!  finally when I try to do it from my .NET Application,  I get the dreaded &quot;SSL Security Error&quot;.  Here's the code for the .NET App:<br />
<br />
Dim con As SqlConnection = New SqlConnection(&quot;SERVER=servername.domainname.com;DATABASE=dbname;U  ID=username;PWD=pass;Encrypt=Yes&quot;)<br />
con.Open()      &lt;--------------------------exception thrown here<br />
<br />
If I remove &quot;Encrypt=Yes&quot; the connection is successful.<br />
<br />
I tried using a Oledbconnection same results.  I tried to use ODBC .net and an ODBCCOnnection. same error.<br />
<br />
Then I tried to create a System DSN with &quot;strong encryption for data&quot;.  I tested the connection in the DSN Configurator....Click on &quot;Test Data Source&quot; button.  Test Successful.  BUt when I use this DSN from my .NET application I get the same error: &quot;<br />
SSL Security Error&quot;.<br />
<br />
I really would like to know if anyone has successfully used a ssl connection from a .net application?!!!???  It couldn't be the certificates!  The certificates common name is fully qualified.....servername.domainname.com<br />
The application runs on the same machine which the sql server runs, but I use the fully qualified servername in the connection string.  (beside i did try to connect from a remote machine, after installed the root test certificates as trusted...still<br />
no luck)<br />
On the machine that the .net application is running, I've imported the root test certificate which was installed as the server.  It is in as &quot;Trusted Root Certification Authority&quot;.  Query analyzer and Enterprise manager seem to work with the ssl encr<br />
ypted connection, so how could it be the certificates?  Even on the webserver there's no security warning when I hit a https page (which means the certificates installed are trusted and valid).  My tests were mainly done with the sql server and the .net s<br />
erver on the same machine however I did try remote machines too with no luck.  This machine has only 1 network card and 1 website in IIS.   There's only 1 ssl certificate installed on this machine.  Anyone have similar problems?????<br />
<br />
THanks!</div></div><hr />


<div class="post"><div class="posttop"><div class="username">Allen</div><div class="date">04-11-04, 09:51 PM</div></div><div class="posttext"><div class="ggap">something</div>Hi Kevin,<br />
<br />
I get the same results if I use the FQDN or the netbios name, however I did get everything straightened out.  I think the problem had something to do with me having multiple certificates installed onto the machine.  I had done so much tweeking that I forg<br />
ot that at one point I did install a certificate to that local machine through MMC.  I usually do it through IIS.  Anyways I removed all certificates on the machine and started over.  Installed 1 certificate (self generated certificate through ms certific<br />
ate server) using IIS.  The certificate has the FQDN and has valid dates and is trusted.  I bounced sql server and viola....worked like a charm.  I'm really excited about that!  Works through query analyzer and through my .NET application (without any kin<br />
d of impersonation) running on the default ASPNET windows user.   I also have to remember to install the root certificates to all my client machines so the server certificate is trusted on each client.<br />
<br />
The next thing I need to figure out is how to have 2 certificates (one for sql and one for my web users IIS).  Its seems pretty clumsy if I install the sql certificate first, start sql server, then install the IIS certificate.  That should work right?  Bu<br />
t what happens if i need to bounce sql server?  Pretty troublesome.  Thanks for you help!<br />
<br />
<br />
<br />
----- Kevin McDonnell &#91;MSFT] wrote: -----<br />
<br />
When you connect to your server using your application does the behavior<br />
change if you use the netbios name<br />
of the SQL Server vs. the FQDN?<br />
<br />
If you can successfully connect from IIS to SQL using Query Analyser, then<br />
any application should be able to as well.  As long as you're using the<br />
same credentials.<br />
<br />
&quot;Then I tried to create a System DSN with &quot;strong encryption for data&quot;.  I<br />
tested the connection in the DSN Configurator....Click on &quot;Test Data<br />
Source&quot; button.  Test Successful.  BUt when I use this DSN from my .NET<br />
application I get the same error: &quot;SSL Security Error&quot;.<br />
&quot;<br />
So testing while you're logged onto the machine allows the connection to<br />
succeed.  It's only from the .net application that fails.  Test using a<br />
Simple ASP page to verify that the connection is working.  There's a sample<br />
you can test with from the enclosed kb article.  If the Sample ASP page<br />
works, then we know it is something about the ASP.NET application.<br />
<br />
319723 INF: SQL Server 2000 Kerberos support including SQL Server virtual<br />
http://support.microsoft.com/?id=319723<br />
<br />
Thanks,<br />
<br />
Kevin McDonnell<br />
Microsoft Corporation<br />
<br />
This posting is provided AS IS with no warranties, and confers no rights.</div></div><hr />


<div class="post"><div class="posttop"><div class="username">Kevin McDonnell [MSFT]</div><div class="date">04-12-04, 05:34 PM</div></div><div class="posttext"><div class="ggap">something</div>From previous post:<br />
<br />
&quot;The next thing I need to figure out is how to have 2 certificates (one for<br />
sql and one for my web users IIS).  Its seems pretty clumsy if I install<br />
the sql certificate first, start sql server, then install the IIS<br />
certificate.  That should work right?  But what happens if i need to bounce<br />
sql server?  Pretty troublesome. &quot;<br />
<br />
SQL and IIS both can use the same certificate if SQL and IIS are on the<br />
same machine.  Both applications rely on certificates for Server<br />
Authentication.  Both applications require that the &quot;Subject&quot; is the fully<br />
qualified domain name of the server.<br />
<br />
The problem with SQL is that the server certificate is only read once.  On<br />
startup.  Once the server is started, any changes to the certificate store<br />
are not read.<br />
<br />
If you have multiple certificates on the same machine, one issued to the<br />
local user and one for SQL issued to the machine, you can tell SQL which<br />
certificate to use by modifying the registry.  I would only recommend doing<br />
this if SQL fails to start.<br />
<br />
<br />
Thanks,<br />
<br />
Kevin McDonnell<br />
Microsoft Corporation<br />
<br />
This posting is provided AS IS with no warranties, and confers no rights.</div></div><hr />

<div id="cbd">vBulletin v3.6.2, Copyright &copy;2000-2010, Jelsoft Enterprises Ltd.</div>
</div>
<SCRIPT language="javascript" src="http://examnotes.us.intellitxt.com/intellitxt/front.asp?IPID=917&MK=10&FG=0000FF&SN=g8,cbd"></SCRIPT>
</body>
</html>