Re: Inheritance is a security loophole!

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Inheritance is a security loophole!
Date: 2000-12-22 20:01:06
Message-ID: 200012222001.PAA01595@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> I suppose a proper fix would involve adding a new permission type "can
> make child tables", but I don't want to mess with that at the moment.
> For 7.1, I propose that we only allow creation of child tables to the
> owner of the parent table.

I see no reason people would be inheriting from other people's tables.
Let's disable it.

> PS: another interesting problem: create a temp table, then create a
> non-temp table that inherits from it. Unhappiness ensues when you
> end your session. Need to prohibit this combination, I think.

Clear example where mixing features causes strange behavour. Part of
the UNION/TEMPORARY/subquery/aggregate/inheritance/rule/view/array mix.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Mikheev, Vadim 2000-12-22 20:14:08 7.1current: order by func in union
Previous Message Mikheev, Vadim 2000-12-22 19:36:16 7.0.3: order by func in union