Postgres Pro
Downloads
Home   >   mailing lists

Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in - Mailing list pgsql-hackers

From Tom Lane
Subject Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in
Date
Msg-id 16673.1029899632@sss.pgh.pa.us
Whole thread Raw
In response to Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow  (Tatsuo Ishii <t-ishii@sra.co.jp>)
List pgsql-hackers
Tree view 
Tatsuo Ishii <t-ishii@sra.co.jp> writes:
> They are like:

>  * conv_proc(
>  *        INTEGER,    -- source encoding id
>  *        INTEGER,    -- destination encoding id
>  *        OPAQUE,        -- source string (null terminated C string)
>  *        OPAQUE,        -- destination string (null terminated C string)
>  *        INTEGER        -- source string length

Got it (shoulda read the documentation before asking ;-))

> The returned integer is actually dummy. The function always returns 1.

Yes.  I will change these to be declared as
foo(int, int, cstring, cstring, int) returns void

unless anyone has a problem with that?
        regards, tom lane

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Build failure in current CVS (src/backend/utils/mb/conversion_procs)
Next
From: Tatsuo Ishii
Date:
Subject: pgstattuple change using SRF