Re: pg_user

From: ivan <iv(at)psycho(dot)pl>
To: Jan Wieck <JanWieck(at)Yahoo(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_user
Date: 2003-10-30 21:10:48
Message-ID: Pine.LNX.4.56.0310302207110.24870@rex.anfa.pl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


you can also patch your kernel and when you write cat /etc/passwd system
give you only your line , whitout any others users, so exacly what you
need ,
in pgsql i think that users dont need to know about others , and also
them
databases, i call it security :)

On Mon, 27 Oct 2003, Jan Wieck wrote:

> ivan wrote:
>
> > hi
> >
> > can we change initdb when view pg_user is createing to :
> >
> > CREATE VIEW pg_user AS \
> > SELECT \
> > usename, \
> > usesysid, \
> > usecreatedb, \
> > usesuper, \
> > usecatupd, \
> > '********'::text as passwd, \
> > valuntil, \
> > useconfig \
> > FROM pg_shadow WHERE usename = SESSION_USER;
>
> No, at least not without a complete proposal how to retain the current
> behaviour of pg_tables, pg_views, psql's \d and other places that rely
> on pg_user being able to display all users.
>
> It's the same thing with your /etc/passwd. chmod o-rwx /etc/passwd will
> hide the usernames but break many utilities. If you don't want someone
> to know all the logins, don't give him one.
>
>
> Jan
>
> --
> #======================================================================#
> # It's easier to get forgiveness for being wrong than for being right. #
> # Let's break this rule - forgive me. #
> #================================================== JanWieck(at)Yahoo(dot)com #
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message scott.marlowe 2003-10-30 21:27:50 Re: pg_user
Previous Message scott.marlowe 2003-10-30 20:53:04 Re: Deadlock problem