| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Marco van Eck <marco(dot)vaneck(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Have an encrypted pgpass file |
| Date: | 2018-07-18 23:25:37 |
| Message-ID: | 10318.1531956337@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> Seems to me that passing %-specifiers to the command would make it more
> useful (%u for "user", "host" etc) -- your command could refuse to give
> you a password for the superuser account for instance but grant one for
> a read-only user.
It would also provide a *very* fertile source of shell-script-injection
vulnerabilities. (Whaddya mean, you tried to use a user name with a
quote mark in it?)
This is exactly the kind of area in which I'm concerned for the
possibility of sloppily-written scripts being a net negative for
security.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2018-07-19 00:07:22 | Re: print_path is missing GatherMerge and CustomScan support |
| Previous Message | Thomas Munro | 2018-07-18 23:21:52 | Re: Postgres, fsync, and OSs (specifically linux) |