Re: Information of pg_stat_ssl visible to all users - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Information of pg_stat_ssl visible to all users
Date
Msg-id CAB7nPqQA9kwX-sC1xkYdf_oVezLE=LN+Q6ZmbTyrgyQPCopOMg@mail.gmail.com
Whole thread
In response to Re: Information of pg_stat_ssl visible to all users  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Information of pg_stat_ssl visible to all users
Re: Information of pg_stat_ssl visible to all users
List pgsql-hackers


On Sun, Aug 30, 2015 at 5:27 AM, Bruce Momjian wrote:
I know I am coming in late here, but I know Heroku uses random user
names to allow a cluster to have per-user databases without showing
external user name details:
[...]
I can see them having problems with a user being able to see the SSL
remote user names of all connected users.

Yep, and I can imagine that this is the case of any company managing cloud nodes with Postgres embedded, and at least to me that's a real concern.
--
Michael

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: to_json(NULL) should to return JSON null instead NULL
Next
From: David Rowley
Date:
Subject: Re: Minor code improvements to create_foreignscan_plan/ExecInitForeignScan