Preventing the schema from being revealed.

From: Ian FREISLICH <if(at)hetzner(dot)co(dot)za>
To: pgsql-admin(at)postgresql(dot)org
Subject: Preventing the schema from being revealed.
Date: 2005-04-06 05:54:03
Message-ID: 20050406055405.C4AF6534FA@svr1.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi

I have quite a complex database system and I want to expose a public
interface to it without exposing my (and my company's) months of
work.

Is there a way to grant usage on a schema so that they can execute
functions without allowing that user to view the structure of the
database and the definitions of all the functions.

Or is the only way to put wrapper functions in the public schema
that are defined 'SECURITY DEFINER' so that they can execute functions
in the api schema, that the public user does not have access to?

I wouldn't mind them viewing the wrapper functions.

--
Ian Freislich

Browse pgsql-admin by date

  From Date Subject
Next Message lista 2005-04-06 06:45:15 Re: Trying to use initlocation
Previous Message Jim C. Nasby 2005-04-05 19:35:08 Re: VACUUM and read-mostly tables