FIX: A hotfix that adds a SecurityBindingElement.AllowInsecureTransport property that allows the mixed-mode secured message to be sent over an unsecured transport in WCF is available for the .NET Framework 3.5 SP1

INTRODUCTION

The hotfix that is described in the article adds an AllowInsecureTransport property in the SecurityBindingElement class for the Microsoft .NET Framework 3.5 Service Pack 1 (SP1). The default value of this property is set to False. When the property is set to True, the mixed-mode secured message can be sent over an unsecured transport in Windows Communication Foundation (WCF) services, such as HTTP. The property should be set to True only when the client and service are in a trusted environment.

Resolution

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only 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 service pack that contains this hotfix.

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

http://support.microsoft.com/contactus/?ws=supportNote 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.

To download this hotfix from the MSDN Code Gallery, visit the following Microsoft Web site:

http://code.msdn.microsoft.com/KB971831
Note The MSDN Code Gallery displays the languages for which the hotfix is available. If you do not see your language listed, it is because the Code Gallery resource page is not available for that language.

Note Alternatively, you can download this hotfix rollup from the following Microsoft Connect Web site:

http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=21953

Prerequisites

You must have .NET Framework 3.5 Service Pack 1 (SP1) installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix if no instance of the .NET Framework is in use.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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 item in Control Panel.

Windows Vista SP2 and Windows Server 2008 SP2, x86-based version:


File name

File version

File size

Date

Time

Platform

Servicemonikersupport.dll

3.0.4506.4135

17,240

25-Jun-2009

06:57

x86

System.runtime.serialization.dll

3.0.4506.4135

970,752

25-Jun-2009

06:57

x86

System.servicemodel.dll

3.0.4506.4135

5,935,104

25-Jun-2009

06:57

x86

Windows Vista SP2 and Windows Server 2008 SP2, x64-based version:


File name

File version

File size

Date

Time

Platform

Servicemonikersupport.dll

3.0.4506.4135

19,288

25-Jun-2009

06:57

x64

System.runtime.serialization.dll

3.0.4506.4135

847,872

25-Jun2009

06:57

x64

System.servicemodel.dll

3.0.4506.4135

5,271,552

25-Jun-2009

06:57

x64

Windows Server 2008 SP2, Itanium-based version

File name

File version

File size

Date

Time

Platform

Servicemonikersupport.dll

3.0.4506.4135

33,640

25-Jun-2009

06:58

IA-64

System.runtime.serialization.dll

3.0.4506.4135

847,872

25-Jun-2009

06:58

IA-64

System.servicemodel.dll

3.0.4506.4135

5,271,552

25-Jun-2009

06:58

IA-64

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

WCF supports three types of security modes - Transport Security, Message Security and Mixed-Mode Security:

  • Transport Security is applied at the transport byte stream below the message layer. The message does not have a Security header and the message does not carry any user authentication data. It is the least flexible in terms of WS-Security usage and it is highly dependent on the transport. It is the fastest in terms of performance.

  • Message Security is applied at the message layer and it is transport independent. It is a point to point security model with maximum flexibility in terms of having the message routed over different transports. WS-Security defines different ways to secure a message and the tokens that can be used. Message Security provides the maximum flexibility in terms of that as well. Message Security is slowest in terms of performance.

  • Mixed-Mode Security is a hybrid between Transport and Message Security. The transport is encrypted and the message contains some user authentication tokens. If the token can provide a key,then it will sign the timestamp in the security header. If the client token is a Asymmetric token then the 'To' header will be signed as well. It is faster than Message Security.

For more information about the SecurityMessageProperty.OutgoingSupportingTokens property in the .NET Framework 4.0, visit the following Microsoft Web site:

http://msdn.microsoft.com/en-us/library/system.servicemodel.security.securitymessageproperty.outgoingsupportingtokens(VS.100).aspx

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×