Microsoft KB Archive/907829

= FIX: You receive an error message in an application that is built on the .NET Framework 1.1 when you enable the &quot;System cryptography Use FIPS compliant algorithms for encryption, hashing, and signing&quot; policy =

Article ID: 907829

Article Last Modified on 3/23/2007

-

APPLIES TO


 * Microsoft .NET Framework 1.1

-





SYMPTOMS
Consider the following scenario:  You enable the System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing policy in the following location:

Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\

 The computer is running the Microsoft .NET Framework 1.1. An application that is built on the .NET Framework 1.1 uses the System.Net.HttpWebRequest method.

In this scenario, you receive the following error message in the application:

System.Net.WebException: The underlying connection was closed: Could not establish secure channel for SSL/TLS.

System.ComponentModel.Win32Exception: The client and server cannot communicate, because they do not possess a common algorithm



CAUSE
This problem occurs because the Transport Layer Security (TLS) 1.0 protocol is disabled in the .NET Framework 1.1. By default, only the Secure Sockets Layer (SSL) 3.0 protocol is enabled.



Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next .NET Framework 1.1 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites
You must apply the .NET Framework 1.1 Service Pack 1 (SP1) before you apply this hotfix.

Restart requirement
You do not have to restart the computer after you apply this hotfix.

File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.



WORKAROUND
To work around this problem, add the following code that enables TLS 1.0 and SSL 3.0 in the application. ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls | SecurityProtocolType.Ssl3



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
By default, TLS 1.0 is also disabled in the Microsoft .NET Framework 1.0. By default, TLS 1.0 and SSL 3.0 are enabled in the Microsoft .NET Framework 2.0.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

For more information about System cryptography, visit the following Microsoft Web site:

http://technet2.microsoft.com/windowsserver/en/library/6ff574cb-30c4-4ad9-8d5e-aee697c65b9b1033.mspx

Keywords: kbwinserv2003sp2fix kbnetframe110presp2fix kbprogramming kbfix kbbug kbqfe kbhotfixserver KB907829

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.