XCLN: How Expired Encryption Key Pairs Work

Last reviewed: April 2, 1997
Article ID: Q152686

The information in this article applies to:

Microsoft Exchange Windows 95 client, versions 4.0 and 5.0
Microsoft Exchange Windows 3.x client, versions 4.0 and 5.0
Microsoft Exchange Windows NT client, versions 4.0 and 5.0
Microsoft Exchange MS-DOS client, versions 4.0 and 5.0

SUMMARY

By default, the Key Management Server in Microsoft Exchange Server provides public/private key encryption pairs that expire after 18 months. This cannot be changed.

MORE INFORMATION

You can still read messages encrypted with your older key pairs. A history of your encryption key pairs is maintained in both the .EPF file for client use, as well as in the KM Server database for key escrow purposes.

Old signatures will fail verification with the following error message:

   A Signature has expired error.

However, all of the other conditions (message not altered, signature not suspended, etc.) will pass.

Additional query words:
Keywords : kbother XCLN
Version : 4.0 5.0
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 2, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.