diff options
| author | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2017-02-06 11:33:58 +0200 |
|---|---|---|
| committer | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2017-02-06 11:34:28 +0200 |
| commit | e8f9fe4ae7ab2784ca42b264f4656249311ddfe4 (patch) | |
| tree | 4a9ed5ef4298105f712611f9c9c401b843185c45 /contrib/pgcrypto/pgp-mpi-openssl.c | |
| parent | b87e1680b98465b002198ae49a4f4f2bce4d129e (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-openssl.c')
| -rw-r--r-- | contrib/pgcrypto/pgp-mpi-openssl.c | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/contrib/pgcrypto/pgp-mpi-openssl.c b/contrib/pgcrypto/pgp-mpi-openssl.c index 87936d0d5f6..afaec16f74d 100644 --- a/contrib/pgcrypto/pgp-mpi-openssl.c +++ b/contrib/pgcrypto/pgp-mpi-openssl.c @@ -75,7 +75,7 @@ bn_to_mpi(BIGNUM *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. @@ -83,8 +83,8 @@ bn_to_mpi(BIGNUM *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. |