]> granicus.if.org Git - postgresql/commit
> I've been experimenting with pgcrypto 0.3 (distributed with
authorBruce Momjian <bruce@momjian.us>
Sun, 13 May 2001 02:17:09 +0000 (02:17 +0000)
committerBruce Momjian <bruce@momjian.us>
Sun, 13 May 2001 02:17:09 +0000 (02:17 +0000)
commit5ee76ac8c070037b311a960d8231e02f75d0c134
tree35d423985bd8ac11ca16e86ce7334077c6437b33
parent904ba3ff69e1402bc2042807fd1d37f8570bfea1
> I've been experimenting with pgcrypto 0.3 (distributed with
> Postgres 7.1.0), and I think I've found a bug.
>
> I compiled Pgcrypto with OpenSSL, using gcc 2.95.4 and
> OpenSSL 0.9.6a (the latest Debian 'unstable' packages).

> web=> select encode(digest('blah', 'sha1'), 'base64');
> FATAL 1:  pg_encode: overflow, encode estimate too small
> pqReadData() -- backend closed the channel unexpectedly.
>         This probably means the backend terminated abnormally
>         before or while processing the request.
> The connection to the server was lost. Attempting reset: Succeeded.

> Is this a bug? Can it be fixed?

This is a bug alright.  And a silly one :)

Marko Kreen
contrib/pgcrypto/encode.c