Re: Restrict permissions on schema to hide pl/pgsql code

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Swanand Kshirsagar <swanandon@xxxxxxxxx>
Subject: Re: Restrict permissions on schema to hide pl/pgsql code
From: "David G. Johnston" <david.g.johnston@xxxxxxxxx>
Date: Wed, 24 Jul 2019 06:28:05 -0700
Cc: "pgsql-admin@xxxxxxxxxxxxxxxxxxxx" <pgsql-admin@xxxxxxxxxxxxxxxxxxxx>
In-reply-to: <CAMn6ZARbP+r=AdDpFG1xC217=+mMVOsqnVBLL4Pf+ktDJt33gA@mail.gmail.com>
References: <CAMn6ZARbP+r=AdDpFG1xC217=+mMVOsqnVBLL4Pf+ktDJt33gA@mail.gmail.com>

On Wednesday, July 24, 2019, Swanand Kshirsagar <swanandon@xxxxxxxxx> wrote:

Isn't revoking permissions from a schema should take care of this situation?

The pl/pgsql function body is stored in pg_catalog which the user still has permission to read. There isn’t a good/supported way to work around this behavior.

David J.

Follow-Ups:
- Re: Restrict permissions on schema to hide pl/pgsql code
  - From: Swanand Kshirsagar

References:
- Restrict permissions on schema to hide pl/pgsql code
  - From: Swanand Kshirsagar

Prev by Date: Restrict permissions on schema to hide pl/pgsql code
Next by Date: Re: pg_locks relation cant be found in pg_class
Previous by thread: Restrict permissions on schema to hide pl/pgsql code
Next by thread: Re: Restrict permissions on schema to hide pl/pgsql code
Index(es):
- Date
- Thread

[Index of Archives] [KVM ARM] [KVM ia64] [KVM ppc] [Virtualization Tools] [Spice Development] [Libvirt] [Libvirt Users] [Linux USB Devel] [Linux Audio Users] [Yosemite Questions] [Linux Kernel] [Linux SCSI] [XFree86]

Powered by Linux