From: Laurenz Albe <laurenz.albe@cybertec.at>
To: David G. Johnston <david.g.johnston@gmail.com>
To: PostgreSQL Documentation <pgsql-docs@lists.postgresql.org>
Subject: Re: Another user complaint regarding visibility of pg_catalog data
Date: Wed, 08 Nov 2023 12:58:58 +0100
Message-ID: <d9d5b22443716abe461ce1b52330ef4139fd3e2d.camel@cybertec.at> (raw)
In-Reply-To: <CAKFQuwb0f30_zD3Dw2sfGuSppSox0mTpAy_V4KCGda_JedQmZQ@mail.gmail.com>
References: <CAKFQuwb0f30_zD3Dw2sfGuSppSox0mTpAy_V4KCGda_JedQmZQ@mail.gmail.com>
On Tue, 2023-11-07 at 12:28 -0700, David G. Johnston wrote:
> This comes up every so often (including today on Discord) and I keep having trouble
> figuring out where to point people for our official assertion and explanation
> for why anyone with a login can view routine bodies, view specifications, and comments.
>
> Is this something we just don't want to go into detail within our documentation,
> or just no one has cared enough to write something up (beyond my first draft back
> then) and form it into a patch?
I am not sure if we can and want to document the "why" (this does not really belong
into the technical documentation), but the fact that most catalog tables can be read
by PUBLIC is worth documenting.
Perhaps here: https://www.postgresql.org/docs/current/catalogs.html
When people ask my "why?", I tend to answer "why not?". It is not a security
problem, in my opinion. Every user is allowed to know that I have a table
"purchase" with a column "credit_card_nr". As long as the permissions are set
correctly, that is no problem. Any attempt to hide that information is at best
"security by obscurity".
Yours,
Laurenz Albe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: laurenz.albe@cybertec.at, david.g.johnston@gmail.com, pgsql-docs@lists.postgresql.org
Subject: Re: Another user complaint regarding visibility of pg_catalog data
In-Reply-To: <d9d5b22443716abe461ce1b52330ef4139fd3e2d.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox