| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: remove internal support in pgcrypto? |
| Date: | 2021-08-24 10:28:42 |
| Message-ID: | YSTJ2tuIWDrFLSMz@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Aug 24, 2021 at 11:13:44AM +0200, Peter Eisentraut wrote:
> So I'm tempted to suggest that we remove the built-in, non-OpenSSL cipher
> and hash implementations in pgcrypto (basically INT_SRCS in
> pgcrypto/Makefile), and then also pursue the simplifications in the OpenSSL
> code paths described in [0].
+1 to remove the internal parts. And the options of the non-OpenSSL
code paths are more limited than the OpenSSL ones, with md5, sha1 and
sha2.
NSS has support for most of the hash implementations pgcrypto makes
use of, as far as I recall.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2021-08-24 10:34:25 | Re: pgstat_send_connstats() introduces unnecessary timestamp and UDP overhead |
| Previous Message | Dilip Kumar | 2021-08-24 10:25:26 | Re: Separate out FileSet from SharedFileSet (was Re: pgsql: pgstat: Bring up pgstat in BaseInit() to fix uninitialized use o) |