Dave Page wrote:
> To be honest I'm not keen to expend time and add to the complexity of
> the code to add obscurity (I can't in good conscience call it
security)
> that is so easily bypassed. This seems kinda like adding an entry
> control system to a door next to a large open window.
>
> Regards
> -Original Message-
> From: Merlin Moncure [mailto:[EMAIL PROTECTED]
> Sent: 16 March 2005 17:20
> To: Dave Page
> Cc: pgadmin-hackers@postgresql.org; pgadmin-hackers@postgresql.org
> Subject: RE: [pgadmin-hackers] prevent users from seeing
> pl/pgsql code in
> Merlin Moncure wrote:
> > Is there any relatively easy way to, uh, prevent your users from
seeing
> > some/all of your pl/pgsql code in pgAdmin? :) A by schema solution
> > would be ideal.
>
> I could think of an additional option for schema names that should be
> treated as system schema (like
> -Original Message-
> From: Dave Page [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 16, 2005 12:06 PM
> To: Merlin Moncure
> Cc: pgadmin-hackers@postgresql.org
> Subject: RE: [pgadmin-hackers] prevent users from seeing pl/pgsql code
in
> pgadmin
>
>
&
> -Original Message-
> From: Merlin Moncure [mailto:[EMAIL PROTECTED]
> Sent: 16 March 2005 16:54
> To: Dave Page
> Cc: pgadmin-hackers@postgresql.org
> Subject: RE: [pgadmin-hackers] prevent users from seeing
> pl/pgsql code in pgadmin
>
> > > I a
> > I also tried hacking the search path and putting a pg_proc table
into
> > the public schema. While this fixed select * from pg_proc
> > (but not /df),
> > pgAdmin still pulled the function source.
>
> Odd - it didn't here. Every query on pg_proc resulted in a message box
> telling me it couldn
Merlin Moncure wrote:
Is there any relatively easy way to, uh, prevent your users from seeing
some/all of your pl/pgsql code in pgAdmin? :) A by schema solution
would be ideal.
I could think of an additional option for schema names that should be
treated as system schema (like the Slony-I and pgA
> -Original Message-
> From: Merlin Moncure [mailto:[EMAIL PROTECTED]
> Sent: 16 March 2005 16:33
> To: Dave Page
> Cc: pgadmin-hackers@postgresql.org
> Subject: RE: [pgadmin-hackers] prevent users from seeing
> pl/pgsql code in pgadmin
>
>
> I also tri
> > Is there any relatively easy way to, uh, prevent your users
> > from seeing
> > some/all of your pl/pgsql code in pgAdmin? :) A by schema solution
> > would be ideal.
>
> Anything we did would be fairly pointless given that there's not much
we
> can do to stop them doing 'SELECT prosrc FROM p
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Merlin Moncure
> Sent: 16 March 2005 16:04
> To: pgadmin-hackers@postgresql.org
> Subject: [pgadmin-hackers] prevent users from seeing pl/pgsql
> code in pgadmin
>
Is there any relatively easy way to, uh, prevent your users from seeing
some/all of your pl/pgsql code in pgAdmin? :) A by schema solution
would be ideal.
Merlin
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTEC
11 matches
Mail list logo
