Re: Crash in pgCrypto?

From: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Mario Weilguni <mweilguni(at)sime(dot)com>
Subject: Re: Crash in pgCrypto?
Date: 2008-06-16 18:48:42
Message-ID: 200806161448.43114.xzilla@users.sourceforge.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Monday 16 June 2008 09:54:16 Alvaro Herrera wrote:
> Mario Weilguni wrote:
> > Could someone using the pgcrypto extension please verify this?
> >
> > SELECT encode(digest(null, 'md5'::text), 'hex');
> > or
> > SELECT digest(null, 'md5');
> >
> > Takes a few seconds, and then crashes the server with a Signal 11. My
> > system is PostgreSQL 8.2.7. Seems to be an unchecked access to memory
> > location 0.
>
> I think the functions were made STRICT recently, and the NULL checks
> were removed, but people with the old definitions of the functions could
> see the crashes. Try removing pgcrypto and recompiling it from a fresh
> release.
>

<broken record>
I still advocate to folks to try to put contrib modules into thier own schemas
whenever possible, so that you have the option of doing pg_dump -N
contribmodule, makes things like this much easier to work around. (And yes,
I've volunteered to patch the contribs with this if we ever decide to make it
the default setup)
</broken record>

--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2008-06-16 19:07:40 Re: pg_stat_statements
Previous Message Martijn van Oosterhout 2008-06-16 18:41:58 Re: Question about Encoding a Custom Type