| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jan Wieck <jan(at)wi3ck(dot)info> |
| Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Possible problem with pgcrypto |
| Date: | 2015-02-05 15:58:53 |
| Message-ID: | 6987.1423151933@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jan Wieck <jan(at)wi3ck(dot)info> writes:
> I have encountered a small instability in the behavior of pgcrypto's
> pgp_sym_decrypt() function. Attached is a script that can reproduce the
> problem. It may have to be run repeatedly because the symptom occurs
> rather seldom.
> What the script does is to encode a small string with pgp_sym_encrypt()
> and then repeatedly try to decrypt it with different "wrong" passwords.
> The expected error message for that is of course
> "Wrong key or corrupt data".
> Every now and then, I get a different error message. Things I've seen are:
Have you tested this with this week's releases? We fixed some
memory-mishandling bugs in pgcrypto ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rémi Cura | 2015-02-05 16:07:27 | Re: How do I bump a row to the front of sort efficiently |
| Previous Message | Jan Wieck | 2015-02-05 15:48:46 | Possible problem with pgcrypto |