Signing Certificate Attribute Specification
draft-ietf-smime-sigattr-01
Document | Type |
Expired Internet-Draft
(smime WG)
Expired & archived
|
|
---|---|---|---|
Author | Jim Schaad | ||
Last updated | 1998-07-07 | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
A set of attacks on SignedData objects have been identified relating to the fact that the certificate to be used when verifying the signature in a SignerInfo is not cryptographically bound into the signature. This leads to a set of attacks where the certificate used to verify the signature is altered leading to possible incorrect results. This document describes these attacks and provides ways to deal with some of the attacks.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)