Re: [HACKERS] Here it is - view permissions] - Mailing list pgsql-hackers

From orion.SAPserv.Hamburg.dsh.de!wieck@sapserv.debis.de
Subject Re: [HACKERS] Here it is - view permissions]
Date
Msg-id m0y6ydG-000BFRC@orion.SAPserv.Hamburg.dsh.de
Whole thread Raw
In response to Re: [HACKERS] Here it is - view permissions]  (The Hermit Hacker <scrappy@hub.org>)
List pgsql-hackers
>
> On Mon, 23 Feb 1998, Bruce Momjian wrote:
>
> > > > Why does views default to 'select' permission for 'public'?
> > > > I think most people will never think of the possibility that others
> > > > will be able to SELECT their data through views.
> > > > Should not 'create view' at least print a NOTICE about this?
> > >
> > >     Considering how much security we are putting around everything
> > > else, is it unreasonably to have both 'create view'/'create table' default
> > > to 'revoke all' to public, and 'grant all' to owner?
> >
> > Most commercial databases don't do this.
>
>     Well, just checked with Wayne (My Oracle Guru) and in Oracle,
> everything is private by default, and you open it up as required/desired
> to other ppl...

    Microsoft SQL server too defaults to private and requires
    explicit GRANT for public.


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#======================================== jwieck@debis.com (Jan Wieck) #

pgsql-hackers by date:

Previous
From: "Vadim B. Mikheev"
Date:
Subject: Re: [HACKERS] Current 6.3 issues
Next
From: The Hermit Hacker
Date:
Subject: Re: [HACKERS] Here it is - view permissions