Ken Tanzer wrote: > > > > The better way to go about that is to not let them have an account on > > the server machine in the first place. Just expose the postmaster port > > (perhaps via ssh tunneling) and let them run psql on their own machines. > Somehow, exposing my database ports to the internet scares me more than > any (possibly crazy) stuff I'm trying to do. :) > > But seriously I think I need to give them accounts--I'm setting up > online instances of a web app, so they have a set of (editable) PHP > files, possibly some storage, a log file, etc. It seemed that setting > each up as its own user was better than going through some uber-process > that had access to all the files. > > Just to be clear, cause I'm a little thick sometimes, it is not possible > to do this? Maybe put them into a chroot() environment, or hack psql to remove \!. No one has asked for this before. -- Bruce Momjian <bruce@xxxxxxxxxx> http://momjian.us EnterpriseDB http://enterprisedb.com + None of us is going to be here forever. + -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
