Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
Cc: nandrews(at)investsystems(dot)co(dot)uk, justin(at)postgresql(dot)org, chriskl(at)familyhealth(dot)com(dot)au, vev(at)michvhf(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in
Date: 2002-08-21 03:13:52
Message-ID: 16673.1029899632@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2002-08-21 03:25:29 pgstattuple change using SRF
Previous Message Tom Lane 2002-08-21 03:10:54 Re: Build failure in current CVS (src/backend/utils/mb/conversion_procs)