Re: Have an encrypted pgpass file
От | Tels |
---|---|
Тема | Re: Have an encrypted pgpass file |
Дата | |
Msg-id | 157cf1504a827b39b2193b177aea311f.squirrel@sm.webmail.pair.com обсуждение исходный текст |
Ответ на | Re: Have an encrypted pgpass file (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Have an encrypted pgpass file
|
Список | pgsql-hackers |
Moin, On Wed, July 18, 2018 7:25 pm, Tom Lane wrote: > Alvaro Herrera <alvherre@2ndquadrant.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?) Little Bobby Tables, we call him. :) I'm also concerned that that would let anybody who could alter the environment then let arbitrary code be run as user postgres. Is this something that poses a risk in addition to the current situation? Best regards, Tels
В списке pgsql-hackers по дате отправления: