diff options
| author | Heikki Linnakangas | 2017-02-06 09:33:58 +0000 |
|---|---|---|
| committer | Heikki Linnakangas | 2017-02-06 09:34:32 +0000 |
| commit | 2a931efb76facac47b499afb64b05ab33ededc10 (patch) | |
| tree | f386a59e3e37ffb4958d26ed13181a1d6f48d954 /contrib/pgcrypto/pgp-mpi-internal.c | |
| parent | c5c755862348ec52007ae18e489be07395cbb023 (diff) | |
Fix typos in comments.
Backpatch to all supported versions, where applicable, to make backpatching
of future fixes go more smoothly.
Josh Soref
Discussion: https://www.postgresql.org/message-id/CACZqfqCf+5qRztLPgmmosr-B0Ye4srWzzw_mo4c_8_B_mtjmJQ@mail.gmail.com
Diffstat (limited to 'contrib/pgcrypto/pgp-mpi-internal.c')
| -rw-r--r-- | contrib/pgcrypto/pgp-mpi-internal.c | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/contrib/pgcrypto/pgp-mpi-internal.c b/contrib/pgcrypto/pgp-mpi-internal.c index ea0620d4852..61106c9b41e 100644 --- a/contrib/pgcrypto/pgp-mpi-internal.c +++ b/contrib/pgcrypto/pgp-mpi-internal.c @@ -140,7 +140,7 @@ bn_to_mpi(mpz_t *bn) } /* - * Decide the number of bits in the random componont k + * Decide the number of bits in the random component k * * It should be in the same range as p for signing (which * is deprecated), but can be much smaller for encrypting. @@ -148,8 +148,8 @@ bn_to_mpi(mpz_t *bn) * Until I research it further, I just mimic gpg behaviour. * It has a special mapping table, for values <= 5120, * above that it uses 'arbitrary high number'. Following - * algorihm hovers 10-70 bits above gpg values. And for - * larger p, it uses gpg's algorihm. + * algorithm hovers 10-70 bits above gpg values. And for + * larger p, it uses gpg's algorithm. * * The point is - if k gets large, encryption will be * really slow. It does not matter for decryption. |