Re: pg_user - Mailing list pgsql-hackers

From ivan
Subject Re: pg_user
Date
Msg-id Pine.LNX.4.56.0310302207110.24870@rex.anfa.pl
Whole thread Raw
In response to Re: pg_user  (Jan Wieck <JanWieck@Yahoo.com>)
Responses Re: pg_user
Re: pg_user
Re: pg_user
List 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@Yahoo.com #
>


pgsql-hackers by date:

Previous
From: "scott.marlowe"
Date:
Subject: Re: Deadlock problem
Next
From: Andrew Dunstan
Date:
Subject: Re: pg_user