| From: | Geoff Winkless <pgsqladmin(at)geoff(dot)dj> |
|---|---|
| To: | Geoff Winkless <pgsqladmin(at)geoff(dot)dj> |
| Cc: | marco(dot)vaneck(at)gmail(dot)com, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Have an encrypted pgpass file |
| Date: | 2018-08-02 09:48:42 |
| Message-ID: | CAEzk6febeWQNFmJjtXkNOcyYFXRjF3i7X_mZYkS_-dzOb4hHHg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2 Aug 2018 at 10:41, I wrote:
> Perhaps you could make your auditors happier by restricting that user's
> permissions to only run a defined function, and make that function do the
> work that the automation script wants? So even if the attacker can access
> the password he will still only be able to run that function? (You could
> even add DOS protection into the function to ensure it's only run so often,
> if you were worried about that.)
>
>
I realise (of course, after I sent this) that I misunderstood the thrust
of your requirement, and that you want the ability to log in *your own user*
without entering your own password. Apologies. Ignore me.
Geoff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2018-08-02 09:50:55 | Re: [PATCH] Improve geometric types |
| Previous Message | Tomas Vondra | 2018-08-02 09:43:45 | Re: New Defects reported by Coverity Scan for PostgreSQL |