Group: pgsql.patches


Subject: pgcrypto: fix for broken solaris openssl, v03
From: tgl@sss.pgh.pa.us (Tom Lane)
Date: 9/28/2007 10:21:35 PM
"Marko Kreen" <markokr@gmail.com> writes: > solaris openssl refuses to handle keys longer than 128bits. > ... > So something like the current patch should be still applied > as a near-term fix. Applied to HEAD and 8.2. I wasn't sure if there was interest in patching further back, or if the patch was meant to work further back. Let me know if you're not happy. > But I'm starting to think that the blowfish > check should be #ifdef __solaris__ only. Has anyone good reasons > why it should apply to everyone? As long as we've got to have the code, we may as well use it --- it's possible that Sun isn't the only vendor who got worried about the crypto export laws. Your caching of the result should be enough to ensure that the overhead is negligible. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org

Subject: pgcrypto: fix for broken solaris openssl, v03
From: tgl@sss.pgh.pa.us (Tom Lane)
Date: 9/29/2007 11:50:52 AM
Zdenek Kotala <Zdenek.Kotala@Sun.COM> writes: > Tom Lane wrote: >> Applied to HEAD and 8.2. I wasn't sure if there was interest in >> patching further back, or if the patch was meant to work further back. >> Let me know if you're not happy. > PostgreSQL 8.1 is shipped with Solaris. We are interesting it to have > backport in 8.1. I tested patch on 8.1.10 and Solaris nevada and works fine. OK, applied to 8.1 too. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend