Skip site navigation (1) Skip section navigation (2)

Re: Default privileges for new databases (was Re: Can't

From: Rod Taylor <rbt(at)zort(dot)ca>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Ron Snyder <snyder(at)roguewave(dot)com>,Peter Eisentraut <peter_e(at)gmx(dot)net>,pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Default privileges for new databases (was Re: Can't
Date: 2002-08-27 03:32:20
Message-ID: 1030419141.33213.1.camel@jester (view raw or flat)
Thread:
Lists: pgsql-hackers
Mostly because a user may explicitly create a database with wanted
permissions, only to have this 'special code' remove them.

I personally intend to immediately revoke permissions on public in
template1, to allow the database owner to grant them as needed.

On Mon, 2002-08-26 at 22:27, Bruce Momjian wrote:
> 
> Sorry, I am confused.  Why can we modify temp's permissions on CREATE
> DATABASE but not public's permissions?
> 
> ---------------------------------------------------------------------------
> 
> Tom Lane wrote:
> > Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > > Have we addressed this?  I don't think so.
> > 
> > No, it's not done yet.  My inclination is
> > 
> > * Template1 has temp table creation and schema creation disabled
> > (disallowed to world) by default.
> > 
> > * CREATE DATABASE sets up new databases with temp table creation allowed
> > to world and schema creation allowed to DB owner only (regardless of
> > what the template database had).  The owner can adjust this default
> > afterwards if he doesn't like it.
> > 
> > It would be nice to lock down the public schema in template1 too, but I
> > see no good way to do that, because CREATE DATABASE can't readily fiddle
> > with protections *inside* the database --- the only games we can play
> > are with the protections stored in the pg_database row itself.  So
> > public's permissions are going to be inherited from the template
> > database, and that means template1's public has to be writable.
> > 
> > Objections anyone?
> > 
> > 			regards, tom lane
> > 
> > ---------------------------(end of broadcast)---------------------------
> > TIP 2: you can get off all lists at once with the unregister command
> >     (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
> > 
> 
> -- 
>   Bruce Momjian                        |  http://candle.pha.pa.us
>   pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
>   +  If your life is a hard drive,     |  13 Roberts Road
>   +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
> 
> http://archives.postgresql.org
> 



In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2002-08-27 03:45:01
Subject: Re: Default privileges for new databases (was Re: Can't
Previous:From: Bruce MomjianDate: 2002-08-27 03:26:16
Subject: Re: ident-des patches

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group