||Just so that when we do go to loser,
I won't have to set it again.
||These are the functions exported by the security library for
implementing Certificate Management Message Formats (CMMF).
This API is designed against July 1998 CMMF draft. Please read this
draft before trying to use this API in an application that use CMMF.
||XXXX Now I have to encrypt encodedRandStr and stash it away.
||These are the definitions needed by the library internally to implement
CMMF. Most of these will be helper utilities for manipulating internal
||All fields marked by a PKIStausInfo in comments is an integer
with the following possible values.
Integer Value Meaning
0 granted- got exactly what you asked for.
1 grantedWithMods-got something like what you asked
for;requester is responsible for ascertainging the
2 rejection-you don't get what you asked for; more
information elsewhere in the message
3 waiting-the request body part has not yet been
processed, expect to hear more later.
4 revocationWarning-this message contains a warning
that a revocation is imminent.
5 revocationNotification-notification that a
revocation has occurred.
6 keyUpdateWarning-update already done for the
oldCertId specified in FullCertTemplate.
||This file will implement the functions related to key recovery in
||This file will contain all routines dealing with creating a
CMMFCertRepContent structure through Create/Set functions.
||These are the enumerations used to distinguish between the different
choices available for the CMMFCertOrEncCert structure.
The Certificate Request Message to be encoded.
A Callback function that the ASN1 encoder calls whenever
the encoder wants to write out some DER encoded bytes.
An opaque pointer that gets passed to the function fn
The function fn will be called multiple times. Look at the
comments in crmft.h where the CRMFEncoderOutputCallback type is
defined for information on proper behavior of the function fn.
SECSuccess if encoding was successful. Any other return value
indicates an error occurred during encoding.
||Just set up the structure so that the message structure
looks like one that was created using the API
||These functions to be implemented in the future if the features
which these functions would implement wind up being needed.
||No extensions to copy.
||This file will contain all declarations common to both
encoding and decoding of CRMF Cert Requests. This header
file should only be included internally by CRMF implementation
||Caller should release or unmark the pool, instead of doing it here.
* But there are NO callers of this function at present...
||Macro that returns PR_TRUE if the pointer is not NULL.
If the pointer is NULL, then the macro will return PR_FALSE.
||Header file with all of the structures and types that will be exported
by the security library for implementation of CRMF.
||It's all implicit tagging.
||This file will contain all routines needed by a client that has
to parse a CMMFCertRepContent structure and retirieve the appropriate
||XXX Why not call CMMF_DestroyCertifiedKeyPair or
* XXX cmmf_DestroyCertOrEncCert ?