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 Raw
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  (Stephen Frost <sfrost@snowman.net>)
Re: Information of pg_stat_ssl visible to all users  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
<div dir="ltr"><br /><div class="gmail_extra"><br /><div class="gmail_quote">On Sun, Aug 30, 2015 at 5:27 AM, Bruce
Momjian<spandir="ltr"></span> wrote:<br /><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex"><spanclass=""> </span>I know I am coming in late here, but I know Heroku uses random user<br />
namesto allow a cluster to have per-user databases without showing<br /> external user name details:<br />[...]<br /> I
cansee them having problems with a user being able to see the SSL<br /> remote user names of all connected users.<span
class="HOEnZb"><fontcolor="#888888"><br /></font></span></blockquote></div><br /></div><div class="gmail_extra">Yep,
andI can imagine that this is the case of any company managing cloud nodes with Postgres embedded, and at least to me
that'sa real concern.<br />-- <br /><div class="gmail_signature">Michael<br /></div></div></div> 

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