Re: Consistent error reporting for encryption/decryption in pgcrypto - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Consistent error reporting for encryption/decryption in pgcrypto
Date
Msg-id 20201030003132.GA1693@paquier.xyz
Whole thread Raw
In response to Consistent error reporting for encryption/decryption in pgcrypto  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: Consistent error reporting for encryption/decryption in pgcrypto  (Georgios Kokolatos <gkokolatos@protonmail.com>)
List pgsql-hackers
On Thu, Oct 29, 2020 at 10:26:54PM +0100, Daniel Gustafsson wrote:
> The attached introduce PXE_ENCRYPT_FAILED and use that for EVP_EncryptUpdate to
> ideally be slightly clearer in case of errors.  Any reason not to do that
> instead of using ERR_GENERIC?

+1.  While looking at that, I was wondering of the potential need of
this error code for other encryption code paths, but it happens that
this is only specific to OpenSSL.  Rijndael or Blowfish don't need
it.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Deleting older versions in unique indexes to avoid page splits
Next
From: Peter Geoghegan
Date:
Subject: Re: Deleting older versions in unique indexes to avoid page splits