Question: how does anyone using mySQL keep their tables safe? I've got two users I'd like mnogo to be using: one, "udm", with a password that no-one but me [and the indexer] knows, that's going to be used to index stuff, including writing it to the database. I want another user, "udm_ro" with a password that anyone who's resouceful enough can find out. Thing is, user udm needs access to any and all of the db that it wants. udm_ro needs to be unable to change the data contained in the database [ergo the name...]. I tried this to revoke everything but select, but it looks like the search part of mnogo writes temporary tables. This is probably a mySQL thing I don't understand, but: GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,DROP ON udmsearch TO udm_ro@localhost; Then I tried to revoke REVOKE INSERT,UPDATE,DELETE,CREATE,DROP ON udmsearch.ndict2,udmsearch.ndict3,udmsearch.ndict4,udmsearch.ndict5,udmsearc h.ndict6,udmsearch.ndict7,udsearch.ndict8,udmsearch.ndict9,udmsearch.ndict10 ,udmsearch.ndict11,udmsearch.ndict12,udmsearch.ndict16,udmsearch.ndict32,udm search.categories,udmsearch.affix,udmsearch.spell,udmsearch.server,udmsearch .url,udmsearch.dict,udmsearch.robots,udmsearch.stopword,udmsearch.qtrack TO udm_ro@localhost; Like so, but mySQL told me where to stick that. I don't understand mySQL well enough to have a clue what's going on, here... Can anyone please help me with this? For those who're wondering if it's necessary, I think there are two problems here: 1: I've mostly solved the problem of people actually getting the passwd with creative use of .htaccess, plus not many people have access to the box I'm using. 2: I haven't tested this thoroughly, but I think that people can write dodgy bits of SQL into the search box and find either a) they can delete tables, or b) mySQL throws a wobbly. Thank-you very much, Gary (-; ______________ If you want to unsubscribe send "unsubscribe udmsearch" to [EMAIL PROTECTED]
