Re: Have an encrypted pgpass file - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Have an encrypted pgpass file
Date
Msg-id 10318.1531956337@sss.pgh.pa.us
Whole thread Raw
In response to Re: Have an encrypted pgpass file  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Have an encrypted pgpass file  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: Have an encrypted pgpass file  ("Tels" <nospam-pg-abuse@bloodgate.com>)
List pgsql-hackers
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?)

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


pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: Postgres, fsync, and OSs (specifically linux)
Next
From: Michael Paquier
Date:
Subject: Re: print_path is missing GatherMerge and CustomScan support