Optional
aInstancePtr: objectA run time mechanism for interface discovery.
NS_OK if the interface is supported by the associated instance, NS_NOINTERFACE if it is not.
aInstancePtr must not be null.
[in] A requested interface IID
[out] A pointer to an interface pointer to receive the result.
Add a cert to a cert DB from a binary string.
nsIX509Cert the resulting certificate
The raw DER encoding of a certificate.
String describing the trust settings to assign the certificate. Decoded by CERT_DecodeTrustString. Consists of 3 comma separated sets of characters, indicating SSL, Email, and Object signing trust. The object signing trust flags are effectively ignored by gecko, but they still must be specified (at least by a final trailing comma) because this argument is passed to CERT_DecodeTrustString.
Add a cert to a cert DB from a base64 encoded string.
nsIX509Cert the resulting certificate
The raw representation of a certificate, encoded as Base 64.
String describing the trust settings to assign the certificate. Decoded by CERT_DecodeTrustString. Consists of 3 comma separated sets of characters, indicating SSL, Email, and Object signing trust. The object signing trust flags are effectively ignored by gecko, but they still must be specified (at least by a final trailing comma) because this argument is passed to CERT_DecodeTrustString.
Asynchronously verify a certificate given a set of parameters. Calls the
verifyCertFinished
function on the provided nsICertVerificationCallback
with the results of the verification operation.
See the documentation for nsICertVerificationCallback.
a succeeding nsresult if the job was dispatched successfully
the certificate to verify
an integer representing the usage to verify for (see SECCertificateUsage in certt.h from NSS)
flags as described above
the (optional) hostname to verify for
the time at which to verify, in seconds since the epoch
the nsICertVerificationCallback that will receive the results of this verification
Export a set of certs and keys from the database to a PKCS#12 file.
Success or the specific error code on failure
Identifies a file that will be filled with the data to be exported.
The array of all certificates to be exported.
Use this to import a stream sent down as a mime type into the certificate database on the default token. The stream may consist of one or more certificates.
The raw data to be imported
The length of the data to be imported
The type of the certificate, see constants in nsIX509Cert
A UI context.
Import certificate(s) from file
Identifies a file that contains the certificate to be imported.
Describes the type of certificate that is going to be imported. See type constants in nsIX509Cert.
Import another person's email certificate into the database.
The raw data to be imported
The length of the data to be imported
A UI context.
Import a PKCS#12 file containing cert(s) and key(s) into the database.
Success or the specific error code on failure. The return values are defined in this file.
Identifies a file that contains the data to be imported.
Import a personal certificate into the database, assuming the database already contains the private key for this certificate.
The raw data to be imported
The length of the data to be imported
A UI context.
Query whether a certificate is trusted for a particular use.
Returns true if the certificate is trusted for the given use.
Obtain the stored trust of this certificate.
The type of the certificate. See nsIX509Cert.
A single bit from the usages constants defined within this interface.
Modify the trust that is stored and associated to a certificate within a database. Separate trust is stored for One call manipulates the trust for one trust type only. See the trust type constants defined within this interface.
Change the stored trust of this certificate.
The type of the certificate. See nsIX509Cert.
A bitmask. The new trust for the possible usages. See the trust constants defined within this interface.
The certificate for which to modify trust.
decoded by CERT_DecodeTrustString. 3 comma separated characters, indicating SSL, Email, and Object signing trust. The object signing trust flags are effectively ignored by gecko, but they still must be specified (at least by a final trailing comma) because this argument is passed to CERT_DecodeTrustString.
Generated using TypeDoc
This represents a service to access and manipulate X.509 certificates stored in a database.