FIX: A hotfix is available that enables SQL Server 2008 Reporting Services and SQL Server 2008 R2 Reporting Services to use a 2048-bit RSA key to encrypt a Reporting Services key for FIPS compliancy

Article translations Article translations
Article ID: 2283072 - View products that this article applies to.
Microsoft distributes Microsoft SQL Server 2008 R2 and Microsoft SQL Server 2008 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 or SQL Server 2008 fix release.
Expand all | Collapse all

SUMMARY

A hotfix is available that enables Microsoft SQL Server 2008 Reporting Services and Microsoft SQL Server 2008 R2 Reporting Services to use a 2048-bit RSA key to encrypt a Reporting Services key.

Before you apply the hotfix, SQL Server 2008 Reporting Services and SQL Server 2008 R2 Reporting Services uses a 1024-bit RSA key to encrypt a 3DES Reporting Services key. As required by Federal Information Processing Standards (FIPS), the minimum length of an RSA key for key transport scheme is 2048 bit since December 31, 2010. This hotfix enables SQL Server 2008 Reporting Services and SQL Server 2008 R2 Reporting Services to still be FIPS compliant after this standard takes effect.

RESOLUTION

Cumulative update information

SQL Server 2008 Service Pack 1 The fix for this issue was first released in Cumulative Update 10 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2279604 Cumulative update 10 for SQL Server 2008 Service Pack 1
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released

Service pack information

The fix is included in SQL Server 2008 Service Pack 2. For more information about how to obtain the latest service pack for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
968382 How to obtain the latest service pack for SQL Server 2008

SQL Server 2008 Service Pack 2

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2289254 Cumulative update 1 for SQL Server 2008 Service Pack 2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2402659 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released

SQL Server 2008 R2

The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2261464 Cumulative update package 3 for SQL Server 2008 R2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

STATUS

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

REFERENCES

For more information about encrypted report server data, visit the following Microsoft Developer Network (MSDN) website:
Storing encrypted report server data
For more information about the how to configure and manage encryption keys, visit the following MSDN website:
Configuring and managing encryption keys
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, 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

Properties

Article ID: 2283072 - Last Review: November 15, 2010 - Revision: 4.0
APPLIES TO
  • Microsoft SQL Server 2008 R2 Reporting Services
  • Microsoft SQL Server 2008 Reporting Services
Keywords: 
kbqfe kbfix kbsurveynew kbexpertiseadvanced KB2283072

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com