Date: Thu, 15 May 2014 15:44:53 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Daniel Gomez Blanco <nanodgb@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Pros and cons of giving someone superuser privilege
Message-ID: <20140515194453.GA25052@momjian.us>
References: 
 <CAL4HELd-Zhk3exeNdk=dxwVsAwXrgnTRfbsCThH3T0=KA33A_w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <CAL4HELd-Zhk3exeNdk=dxwVsAwXrgnTRfbsCThH3T0=KA33A_w@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

On Fri, Apr 25, 2014 at 03:46:52PM +0200, Daniel Gomez Blanco wrote:
> Hi all,
> 
> I'm part of a service where we provide users with their own PostgreSQL
> instances. The idea is that we provide them with a website to request and
> manage their databases (start/stop, backups, restores, upgrades, monitoring,
> etc). By doing this, we avoid having to give them access to the machine where
> their database is running, as this would be a security concern. But in the end,
> the user is the sole responsible for the database.
> 
> At the moment we create an "admin" user for them and give it "createdb" and
> "createrole" privileges. My question is, in case we give that user the
> superuser privilege, what would the repercussion be concerning security (as in

Have you considered that your users can _create_ superusers?  I think
modified Amazon Postgres blocks that, but native Postgres does not.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + Everyone has their own god. +


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin