On Tue, May 27, 2003 at 01:50:48AM -0700, p dont think wrote: > > 3. Set up preferences to be taken from a database. You could then do > > something as simple as making the preferences table read-only to > > SquirrelMail (or, to be precise, to the user account through which SM > > connects to the database). > > again, denying access to resources that SM assumes it will have is not a > good way to solve this problem.
Not if you are using a smart RDBMS. Then you could point SquirrelMail at a view rather than a genuine table. It wouldn't be hard with Postgres or SQL server to have a view that showed you all your preferences when you read to it but silently discarded certain updates or inserts. -- Bruce The ice-caps are melting, tra-la-la-la. All the world is drowning, tra-la-la-la-la. -- Tiny Tim.
pgp00000.pgp
Description: PGP signature
