Re: [PATCH] Add enable_copy_program GUC to control COPY PROGRAM
| От | Kirill Reshke |
|---|---|
| Тема | Re: [PATCH] Add enable_copy_program GUC to control COPY PROGRAM |
| Дата | |
| Msg-id | CALdSSPiZ0pj6Eh4rtoQE9=8n+O_Q4RmpVj+zsx52mxJWT1S7Yw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [PATCH] Add enable_copy_program GUC to control COPY PROGRAM (Jelte Fennema-Nio <postgres@jeltef.nl>) |
| Ответы |
Re: [PATCH] Add enable_copy_program GUC to control COPY PROGRAM
Re: [PATCH] Add enable_copy_program GUC to control COPY PROGRAM |
| Список | pgsql-hackers |
On Thu, 4 Dec 2025 at 21:33, Jelte Fennema-Nio <postgres@jeltef.nl> wrote: > > On Thu, 4 Dec 2025 at 11:56, Kirill Reshke <reshkekirill@gmail.com> wrote: > > > One idea would be to disallow FROM PROGRAM when connecting over the > > network instead of a Unix socke > > > > How this would be protected from connecting to PostgreSQL over the > > network and then executing dblink, making local (socket) connection? > > Good question. I think the easiest would be to always disallow FROM > PROGRAM (by default) instead of only when connecting over the network. How? with GUC? > Another option would be to have dblink (and pg_fdw) tell postgres (wih > e.g. a GUC being set in the StartupMessage) that it should be > considered a remote connection for these purposes. Again, if we are using GUC to tell somebody something about security, this doesn't work. Superuser can easily redefine any GUC. -- Best regards, Kirill Reshke
В списке pgsql-hackers по дате отправления: