its vs it\'s etc. From Bjorn Sandell
git-svn-id: svn://svn.h5l.se/heimdal/trunk/heimdal@22071 ec53bebd-3082-4978-b11e-865c3cabbd6b
This commit is contained in:
@@ -55,7 +55,7 @@ certificate request
|
||||
|
||||
x509 issues:
|
||||
|
||||
OtherName is left unspecified, but its used by other
|
||||
OtherName is left unspecified, but it's used by other
|
||||
specs. creating this hole where a application/CA can't specify
|
||||
policy for SubjectAltName what covers whole space. For example, a
|
||||
CA is trusted to provide authentication but not authorization.
|
||||
|
@@ -695,7 +695,7 @@ _hx509_cert_is_parent_cmp(const Certificate *subject,
|
||||
memset(&si, 0, sizeof(si));
|
||||
|
||||
/*
|
||||
* Try to find AuthorityKeyIdentifier, if its not present in the
|
||||
* Try to find AuthorityKeyIdentifier, if it's not present in the
|
||||
* subject certificate nor the parent.
|
||||
*/
|
||||
|
||||
@@ -789,7 +789,7 @@ certificate_is_self_signed(const Certificate *cert)
|
||||
}
|
||||
|
||||
/*
|
||||
* The subjectName is "null" when its empty set of relative DBs.
|
||||
* The subjectName is "null" when it's empty set of relative DBs.
|
||||
*/
|
||||
|
||||
static int
|
||||
|
@@ -1045,7 +1045,7 @@ hx509_cms_create_signed_1(hx509_context context,
|
||||
}
|
||||
|
||||
/*
|
||||
* If its not pkcs7-data send signedAttributes
|
||||
* If it isn't pkcs7-data send signedAttributes
|
||||
*/
|
||||
|
||||
if (der_heim_oid_cmp(eContentType, oid_id_pkcs7_data()) != 0) {
|
||||
|
@@ -1,4 +1,4 @@
|
||||
This is a static file don't change the content, its used in the test
|
||||
This is a static file don't change the content, it is used in the test
|
||||
|
||||
#!/bin/sh
|
||||
#
|
||||
|
@@ -403,7 +403,7 @@ p11_get_session(hx509_context context,
|
||||
* prompter or known to work pin code.
|
||||
*
|
||||
* This code is very conversative and only uses the prompter in
|
||||
* the hx509_lock, the reason is that its bad to try many
|
||||
* the hx509_lock, the reason is that it's bad to try many
|
||||
* passwords on a pkcs11 token, it might lock up and have to be
|
||||
* unlocked by a administrator.
|
||||
*
|
||||
|
@@ -151,7 +151,7 @@ verify_ocsp(hx509_context context,
|
||||
|
||||
/*
|
||||
* If signer certificate isn't the CA certificate, lets check the
|
||||
* its the CA that signed the signer certificate and the OCSP EKU
|
||||
* it is the CA that signed the signer certificate and the OCSP EKU
|
||||
* is set.
|
||||
*/
|
||||
if (hx509_cert_cmp(signer, parent) != 0) {
|
||||
@@ -415,7 +415,7 @@ verify_crl(hx509_context context,
|
||||
_hx509_query_clear(&q);
|
||||
|
||||
/*
|
||||
* If its the signer have CRLSIGN bit set, use that as the signer
|
||||
* If it's the signer have CRLSIGN bit set, use that as the signer
|
||||
* cert for the certificate, otherwise, search for a certificate.
|
||||
*/
|
||||
if (_hx509_check_key_usage(context, parent, 1 << 6, FALSE) == 0) {
|
||||
@@ -1016,8 +1016,8 @@ hx509_revoke_ocsp_print(hx509_context context, const char *path, FILE *out)
|
||||
}
|
||||
|
||||
/*
|
||||
* Verify that the `cert' is part of the OCSP reply and its not
|
||||
* expired. Doesn't verify signature the OCSP reply or its done by a
|
||||
* Verify that the `cert' is part of the OCSP reply and it's not
|
||||
* expired. Doesn't verify signature the OCSP reply or it's done by a
|
||||
* authorized sender, that is assumed to be already done.
|
||||
*/
|
||||
|
||||
|
Reference in New Issue
Block a user