| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Greg Sabino Mullane" <greg(at)turnstep(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: LISTEN filtering |
| Date: | 2011-06-21 16:07:51 |
| Message-ID: | 15884.1308672471@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Greg Sabino Mullane" <greg(at)turnstep(dot)com> writes:
> Quick idea to toss out there: allowing an option to LISTEN to
> only 'hear' from superusers (or self).
This seems like a pretty bad idea from a security policy standpoint,
in that it would encourage use of superuser state to run ordinary
applications.
> I've got an app that uses a lot
> of listen/notify to talk to other subprocesses. However, it
> would be nice if non-superusers could not affect the behavior
> of this application: right now, anyone can issue a NOTIFY.
Anyone connected to the same database, yes. Can't you just restrict use
of the database to trustworthy apps?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-06-21 16:25:19 | Re: Partitioning and constraint exclusion |
| Previous Message | Sylvain Rabot | 2011-06-21 15:58:20 | Partitioning and constraint exclusion |