| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Information of pg_stat_ssl visible to all users |
| Date: | 2015-08-30 15:35:41 |
| Message-ID: | 20150830153541.GJ31526@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2015-08-30 11:33:28 -0400, Stephen Frost wrote:
> Yeah, I'm not really thrilled with all of this information being
> available to everyone on the system. We already get ding'd by people
> for not limiting who can see what connections there are to the database
> and this is doubling-down on that.
I don't buy that the relevant piece of information is the CN when the
connection itself is visible. Neither do I buy the argument that later
hiding this for ssl once we have more granular permissions is going to
be relevantly painful in comparison to changing the contents of
pg_stat_activity itself.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2015-08-30 15:39:25 | Re: SimpleTee flush |
| Previous Message | Stephen Frost | 2015-08-30 15:33:28 | Re: Information of pg_stat_ssl visible to all users |