Re: pg_largeobject is a security hole - Mailing list pgsql-hackers

From Philip Warner
Subject Re: pg_largeobject is a security hole
Date
Msg-id 3.0.5.32.20010628095414.03614100@mail.rhyme.com.au
Whole thread Raw
In response to Re: pg_largeobject is a security hole  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
At 19:49 27/06/01 -0400, Tom Lane wrote:
>
>Hmm.  [sound of grepping]  So does psql's \lo_list command.  That's
>annoying ... the list of large object OIDs is *exactly* what you'd want
>to hide from the unwashed masses.  Oh well, I'll leave bad enough alone
>for now.
>

I suspect this would be cleaned up when/if we implement LOB LOCATORs: they
have a limited lifetime, should be the only way to retrieve LOBs, and could
hide the underlying OID (which would never be used by external interfaces).


----------------------------------------------------------------
Philip Warner                    |     __---_____
Albatross Consulting Pty. Ltd.   |----/       -  \
(A.B.N. 75 008 659 498)          |          /(@)   ______---_
Tel: (+61) 0500 83 82 81         |                 _________  \
Fax: (+61) 0500 83 82 82         |                 ___________ |
Http://www.rhyme.com.au          |                /           \|                                |    --________--
PGP key available upon request,  |  /
and from pgp5.ai.mit.edu:11371   |/


pgsql-hackers by date:

Previous
From: Philip Warner
Date:
Subject: Re: Re: 7.2 items
Next
From: Alex Pilosov
Date:
Subject: Re: functions returning records