FIX: Software Publisher Certificate Verification Is Ignored During Policy Resolution (326477)


The information in this article applies to:

  • Microsoft .NET Framework 1.0 SP1
This article was previously published under Q326477

SYMPTOMS

If you have a Microsoft .NET Framework security policy that requires a Software Publisher Certificate (SPC) for code to run, you may find that you can still run an assembly that is signed with a certificate, although the assembly has been changed in some way.

RESOLUTION

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 Visual Studio .NET service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone 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 typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix has the file attributes (or later) 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. 
   Date          Time    Version        Size        File name  
   ------------------------------------------------------------------
   18-Jul-2002   23:26   1.0.3705.297      65,536   CORPerfMonExt_dll
   19-Jul-2002   12:05   1.0.3705.297   1,953,792   Mscorlib.dll
   18-Jul-2002   23:26   1.0.3705.297   2,265,088   Mscorwks.dll
   18-Jul-2002   23:25   1.0.3705.297   2,265,088   Mscorsvr.dll

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

You can turn on the SPC security policy through the Microsoft .NET Framework Configuration utility. To do this, give Nothing privileges to all code, and then create a group that has full permissions if there is a publisher certificate.

You can only install the fix package in the "Resolution" section on computers that have Microsoft .NET Framework Service Pack 1 installed.

If you must have Service Pack 2 together with this fix, see the following article in the Microsoft Knowledge Base:

328544 INFO: Post-Service Pack 2 .NET Framework Hotfix Rollup Package 1

For additional information about how to get service packs for the Microsoft .NET Framework, click the article number below to view the article in the Microsoft Knowledge Base:

318836 INFO: How to Obtain the Latest .NET Framework Service Pack

Modification Type:MinorLast Reviewed:10/11/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix kbNetFrame100preSP3fix kbQFE KB326477
©2004 Microsoft Corporation. All rights reserved.