We wouldn't make any of the system users a superuser in Postgres and in my 20+ years experience in the industry we provide software for, the possibility of having any users of the system that are able to hack or even understand what they have if they were able to is slim. I understand that anything can be reverse engineered. I had a relationship with a Russian program several years ago that could take the compile C modules, reverse engineer them to assembler and then back to the original C code to find and report bugs. That being said I don't worry too much about those types. Best Regards Michael Gould "Andrew Sullivan" <ajs@xxxxxxxxxxxxxxx> wrote: > On Thu, Apr 07, 2011 at 07:46:36AM -0500, Michael Gould wrote: >> We want to protect the intellectual property of several of our stored >> procedures. If we put them in a separate schema in the database and only >> allow execute on anything in that schema would that protect our stored >> procedures? > > If your customer can have superuser access on the machine (which > effectively means, "If your customer has control of the box,") then > no, it won't. > > If you need to do this sort of thing, then you need to write the > procedures in C and deliver only object code. Even that probably > won't solve everything. > > A > > -- > Andrew Sullivan > ajs@xxxxxxxxxxxxxxx > > -- > Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general > -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
