Hi Bruce,
Thanks for reply.
I've give up: i've found a slide in percona site about pgcrypto that said
the developers of plugin intentionally introduces time consuming code to
prevent brute force attacks.
My queries involves pgcrypto only in a small number of record (about 2000),
so at the end
On Mon, Jan 2, 2023 at 05:57:38PM +0100, aghart...@gmail.com wrote:
> So, a test with pgcrypto:
>
> select pgp_sym_encrypt(data::text, 'pwd') --default to aes128
> from generate_series('2022-01-01'::timestamp, '2022-12-31'::timestamp, '1
> hour'::interval) data
>
> vs
>
> select
Hi,
I see, I was hoping that wasn't the case.
Thanks a lot for your support.
My best regards,
Agharta
Il 03/01/23 16:54, Peter Eisentraut ha scritto:
On 02.01.23 17:57, aghart...@gmail.com wrote:
select pgp_sym_encrypt(data::text, 'pwd') --default to aes128
from
On 02.01.23 17:57, aghart...@gmail.com wrote:
select pgp_sym_encrypt(data::text, 'pwd') --default to aes128
from generate_series('2022-01-01'::timestamp, '2022-12-31'::timestamp,
'1 hour'::interval) data
vs
select pgp_sym_encrypt(data::text, 'pwd','cipher-algo=bf') -- blowfish
from
Hi all,
A question, may I wrong.
I've a Rocky Linux 8 with OpenSSL 1.1.1 FIPS and Intel cpu with aes
support (cat /proc/cpuinfo | grep aes)
Test made with openssl gives me a huge performance with aes enabled vs not:
"openssl speed -elapsed -evp aes-128-cbc" is about 5 time faster than
