On Tue, Sep 29, 2020 at 12:25:05PM +0200, Daniel Gustafsson wrote: > The attached adds config loading to pgcrypto for < 1.1.0 and a doc notice for > enabling the legacy provider in 3.0.0. This will require an alternative > output > file for non-legacy configs, but that should wait until 3.0.0 is GA since the > returned error messages have changed over course of development and may not be > set in stone just yet.
FWIW, testing with 3.0.0-alpha9 dev (2d84089), I can see that the error we have in our SSL tests when using a wrong password in the private PEM key leads now to "PEM lib" instead of "bad decrypt". Upthread, we had "nested asn1 error": https://www.postgresql.org/message-id/9ce70af4-e1a0-4d24-86fa-4c3067077...@yesql.se It looks like not everything is sorted out there yet. pgcrypto is also throwing new errors. Daniel, what if we let this patch aside until upstream has sorted out their stuff? -- Michael
signature.asc
Description: PGP signature
