From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Sean Chittenden <sean(at)chittenden(dot)org> |
Cc: | Alex Rodin <alx(at)sm(dot)ukrtel(dot)net>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: PostgreSQL 7.3.3 with pgcrypto on FreeBSD 5.1 |
Date: | 2003-08-01 05:02:24 |
Message-ID: | 5308.1059714144@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Sean Chittenden <sean(at)chittenden(dot)org> writes:
> FWIW, I can confirm this, but I don't think it's a FreeBSD specific
> problem given that the backend dies inside of an OpenSSL routine.
> #0 0x2864ae9c in EVP_DigestUpdate () from /usr/lib/libcrypto.so.3
> #1 0x28576a90 in px_find_cipher () from /usr/local/lib/postgresql/pgcrypto.so
> #2 0x2857c584 in px_crypt_md5 () from /usr/local/lib/postgresql/pgcrypto.so
By chance I noticed this entry in the CVS logs:
2002-11-14 21:54 momjian
* contrib/pgcrypto/openssl.c: OpenSSL 0.9.6g in Debian/unstable
stopped working with pgcrypto. This is pgcrypto bug as it assumed
too much about inner workings of OpenSSL.
Following patch stops pgcrypto using EVP* functions for ciphers and
lets it manage ciphers itself.
This patch supports Blowfish, DES and CAST5 algorithms.
Marko Kreen
Perhaps the problem is that Marko didn't fix the crypt() code in the
same way?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Oscar Estevez Lopez | 2003-08-01 11:39:59 | extract and time zones |
Previous Message | Tom Lane | 2003-08-01 02:57:56 | Re: PostgreSQL 7.3.3 with pgcrypto on FreeBSD 5.1 |