From: | Reece Hart <reece(at)harts(dot)net> |
---|---|
To: | Steve Crawford <scrawford(at)pinpointresearch(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: password-less access, without using pg_hba |
Date: | 2014-02-09 00:28:16 |
Message-ID: | CAKNDN-dB7bg7nO8APQD1+Otkcm-kyav6xcUS8EM0qpzzh9DBag@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Feb 7, 2014 at 8:27 AM, Steve Crawford <
scrawford(at)pinpointresearch(dot)com> wrote:
> Ignoring the scary security issues....
>
One of the niceties of an RDS deployment is that I don't care much about
the security issues: The machine is not in our VPC, there's only public
data on it, and I presume that AWS has isolated the instance to their
satisfaction. From my point of view, it's an ideal way to make data public
and way better than running it ourselves.
If you can't access pg_hba.conf how about just sticking pgbouncer or
> similar in the middle and have your users connect through that?
>
I like the pgbouncer idea in principle, but it means more work for me that
I'm not willing to take on for this use.
Thanks everyone for the input. I'll stick with an advertised password.
-Reece
From | Date | Subject | |
---|---|---|---|
Next Message | Andrus | 2014-02-09 21:03:53 | How to distribute budget value to actual rows in Postgresql |
Previous Message | David Johnston | 2014-02-09 00:21:56 | Re: Dynamic insert into ARRAY? plpgsql |