security-and-privacy/gnupg
security-and-privacy/gnupg
1
0
Fork 0
mirror of git://git.gnupg.org/gnupg.git synced 2025-07-03 22:56:33 +02:00
Code Activity

indent: Fix spelling

Browse source 
--

These are non-substantive corrections for minor spelling mistakes
within the GnuPG codebase.

With something like this applied to the codebase, and a judiciously
tuned spellchecker integrated as part of a standard test suite, it
should be possible to keep a uniform orthography within the project.

GnuPG-bug-id: 7116
This commit is contained in:
Daniel Kahn Gillmor 2024-05-12 18:09:23 -04:00 • committed by Werner Koch
parent 253a701ed7
commit 42b0e9558a
No known key found for this signature in database
GPG key ID: E3FDFF218E45B72B
136 changed files with 233 additions and 233 deletions
Download patch file Download diff file Expand all files Collapse all files

8
dirmngr/ocsp.c
View file

@ -31,7 +31,7 @@
#include "certcache.h"
#include "ocsp.h"
/* The maximum size we allow as a response from an OCSP reponder. */
/* The maximum size we allow as a response from an OCSP responder. */
#define MAX_RESPONSE_SIZE 65536
@ -526,7 +526,7 @@ check_signature_core (ctrl_t ctrl, ksba_cert_t cert, gcry_sexp_t s_sig,
/* Check the signature of an OCSP response. OCSP is the context,
S_SIG the signature value and MD the handle of the hash we used for
the response. This function automagically finds the correct public
key. If SIGNER_FPR_LIST is not NULL, the default OCSP reponder has been
key. If SIGNER_FPR_LIST is not NULL, the default OCSP responder has been
used and thus the certificate is one of those identified by
the fingerprints. */
static gpg_error_t
@ -651,7 +651,7 @@ check_signature (ctrl_t ctrl,
or directly through the CERT object is valid by running an OCSP
transaction. With FORCE_DEFAULT_RESPONDER set only the configured
default responder is used. If R_REVOKED_AT or R_REASON are not
NULL and the certificat has been revoked the revocation time and
NULL and the certificate has been revoked the revocation time and
the reasons are stored there. */
gpg_error_t
ocsp_isvalid (ctrl_t ctrl, ksba_cert_t cert, const char *cert_fpr,
@ -723,7 +723,7 @@ ocsp_isvalid (ctrl_t ctrl, ksba_cert_t cert, const char *cert_fpr,
}
/* Figure out the OCSP responder to use.
1. Try to get the reponder from the certificate.
1. Try to get the responder from the certificate.
We do only take http and https style URIs into account.
2. If this fails use the default responder, if any.
*/