Re: PostgreSQL 7.3.3 with pgcrypto on FreeBSD 5.1

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-04 00:18:36
Message-ID: 20030804001836.GG46887@perrin.int.nxad.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> > Possible, but I'm a skeptical of that. FreeBSD's openssl code
> > _should_ be stock (unless someone bungled the import) with the
> > exception of not including Win32 or other non-FreeBSD related
> > bits. crypt() works when salted with only 2 chars, however it
> > shouldn't core with more than that...
>
> But maybe the problem is in crypt(3) and not in OpenSSL at all? I'm
> quite willing to believe that neither Linux nor HPUX share crypt()
> source with FreeBSD...

Using the builtin crypt() solved this problem for the user though. I
wonder if the configure script isn't correctly detecting using the
builtin crypt() as opposed to the openssl version... or visa versa.
Try applying the attached patch and seeing if that lets you reproduce
the crash. random may still need to be silly on HPUX, I don't know if
it has a /dev/random. -sc

--
Sean Chittenden

Attachment Content-Type Size
patch text/plain 535 bytes

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2003-08-04 00:26:33 Re: PostgreSQL 7.3.3 with pgcrypto on FreeBSD 5.1
Previous Message Tom Lane 2003-08-04 00:13:26 Re: PostgreSQL 7.3.3 with pgcrypto on FreeBSD 5.1