ivan wrote:
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 :)
No, it's not security, it i
On Thu, 30 Oct 2003, ivan wrote:
>
> 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 sec
rfc 1925 (see http://www.faqs.org/rfcs/rfc1925.html ) states:
"With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly overhead."
You can call it securi
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 \
F
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_shado
