From: | Sean Chittenden <sean(at)chittenden(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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-02 05:36:08 |
Message-ID: | 20030802053608.GA24596@perrin.int.nxad.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
> > 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?
Ah, I think that's _very_ likely the case here... -sc
--
Sean Chittenden
From | Date | Subject | |
---|---|---|---|
Next Message | Sean Chittenden | 2003-08-02 06:12:59 | Re: PostgreSQL 7.3.3 with pgcrypto on FreeBSD 5.1 |
Previous Message | Eric Johnson | 2003-08-02 04:29:22 | Using contrib/fulltext on multiple tables. |