Re: pgp_sym_decrypt() - error 39000: wrong key or corrupt data - Mailing list pgsql-general

From Adrian Klaver
Subject Re: pgp_sym_decrypt() - error 39000: wrong key or corrupt data
Date
Msg-id 94ecaa31-5960-6264-81f9-c8560a3f9fed@aklaver.com
Whole thread Raw
In response to pgp_sym_decrypt() - error 39000: wrong key or corrupt data  (Moreno Andreo <moreno.andreo@evolu-s.it>)
Responses Re: pgp_sym_decrypt() - error 39000: wrong key or corrupt data
List pgsql-general
On 06/21/2018 08:36 AM, Moreno Andreo wrote:
> Hi,
>      while playing with pgcrypto I ran into a strange issue (postgresql 
> 9.5.3 x86 on Windows 7)
> 
> Having a table with a field
> dateofbirth text
> 
> I made the following sequence of SQL commands
> update tbl_p set dateofbirth = pgp_sym_encrypt('2018-06-21', 'AES_KEY') 
> where codguid = '00000001-0001-0001-0001-000000000001';
> OK
> 
> select pgp_sym_decrypt(dateofbirth::bytea, 'AES_KEY') as datanasc from 
> tbl_p where codguid = '00000001-0001-0001-0001-000000000001'
> '2018-06-21'
> 
> select * from tab_paz where pgp_sym_decrypt(natoil::bytea, 'AES_KEY') = 
> '2018-06-21'

You switched gears above.

What is the data type of the natoil field in table tab_paz?

Was the data encrypted in it using the 'AES_KEY'?

I can replicate the below by doing:

select pgp_sym_decrypt(pgp_sym_encrypt('2018-06-21', 'AES_KEY'), 'AES');
ERROR:  Wrong key or corrupt data


> ERROR:  Wrong key or corrupt data
> ********** Error **********
> 
> ERROR: Wrong key or corrupt data
> SQL state: 39000
> 
> Can't find reference anywhere...
> Any help would be appreciated.
> Thanks,
> Moreno.-
> 
> 
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: SQL Query never ending...
Next
From: David Pacheco
Date:
Subject: Re: Can PostgreSQL create new WAL files instead of reusing old ones?