OL2000: E-Mail Is Sent with 40-Bit Encryption Instead of 128-Bit Encryption (816787)
The information in this article applies to:
- Microsoft Outlook 2000 Service Pack 3 (SP-3)
IMPORTANT: This article contains information about modifying the registry.
Before you modify the registry, make sure to back it up and make sure that you
understand how to restore the registry if a problem occurs. For information
about how to back up, restore, and edit the registry, click the following
article number to view the article in the Microsoft Knowledge Base: 256986 Description of the Microsoft Windows Registry SYMPTOMSWhen you send an encrypted e-mail message from Outlook 2000,
you may not be warned that it has been encrypted with 40-bit encryption instead
of 128-bit encryption. This symptom may occur after you have updated your copy
of Office 2000 with the Office 2000 Service Pack 3 (SP3) patch.WORKAROUNDWARNING: If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Microsoft
cannot guarantee that you can solve problems that result from using Registry
Editor incorrectly. Use Registry Editor at your own risk.
Follow these steps, and then quit Registry Editor:
- Click Start, click Run,
type regedit, and then click OK.
- Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINE\Software\Microsoft\Office\9.0\Outlook\Security - On the Edit menu, point to
New, and then click REG_DWORD.
- Type
UseAlternateDefaultEncryptionAlg, and then press ENTER.
- On the Edit menu, click
Modify.
- Type 1, and then click
OK.
The value 1 enables 128-bit encryption of your e-mail messages. The value 0 leaves encryption at the 40-bit encryption level. If you set the
value to 0, you receive the following warning message when you send
encrypted e-mail messages: This message will be
encrypted using a 40 bit key so that all recipients can decrypt and read it.
This may not be the security level that you want. Do you want to send this
message? STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are
listed at the beginning of this article.
Modification Type: | Major | Last Reviewed: | 3/26/2003 |
---|
Keywords: | kbnofix kbprb KB816787 |
---|
|