Re: Special role for subscriptions

From: Evgeniy Efimkin <efimkin(at)yandex-team(dot)ru>
To: Michael Paquier <michael(at)paquier(dot)xyz>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
Cc: Euler Taveira <euler(at)timbira(dot)com(dot)br>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Дмитрий Сарафанников <dsarafan(at)yandex-team(dot)ru>, Владимир Бородин <root(at)simply(dot)name>
Subject: Re: Special role for subscriptions
Date: 2019-03-22 08:06:06
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

> These are basically that the truncate, insert, delete and insert
> rights for the role creating the subscription. Why would we actually
> need that?
It's for security reasons. Because possible to attack target server. If publication have system tables for instance pg_authid

> pg_subscription_users and these should be able to dump subscriptions,
> so you have at least one problem.
But in system_views.sql we give grant on subconninfo column and pg_dump required superuser privilege only for postgesql under 12 version. Old version pg_dump still works but require superuser for dump subscription.

Efimkin Evgeny

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Banck 2019-03-22 08:13:43 Re: Offline enabling/disabling of data checksums
Previous Message Alexander Korotkov 2019-03-22 08:05:05 Re: Connections hang indefinitely while taking a gin index's LWLock buffer_content lock