Signature specification without certificates
- From: "James H. Markowitz" <noone@xxxxxxxxxxx>
- Date: Mon, 21 Sep 2009 17:11:40 +0000 (UTC)
Signatures are inambiguously specified when embedded in an X.509
certificate, as per the following ASN.1 defined in RFC 3280:
Certificate ::= SEQUENCE {
tbsCertificate TBSCertificate,
signatureAlgorithm AlgorithmIdentifier,
signatureValue BIT STRING
}
How does one specify signatures without using certificates? I guess one
could use a type like
SignatureInfo ::= SEQUENCE {
signatureAlgorithm AlgorithmIdentifier,
signatureValue BIT STRING
}
However, I have yet to find an RFC or some other standard in which such a
thing is discussed. Can anybody help?
.
- Follow-Ups:
- Re: Signature specification without certificates
- From: Anne & Lynn Wheeler
- Re: Signature specification without certificates
- From: Tom St Denis
- Re: Signature specification without certificates
- From: Bruce Stephens
- Re: Signature specification without certificates
- Prev by Date: Re: What About LibTomCrypt?
- Next by Date: Re: Signature specification without certificates
- Previous by thread: What About LibTomCrypt?
- Next by thread: Re: Signature specification without certificates
- Index(es):
Relevant Pages
|