> TMDA "whitelists" are flat text files with a simple and easily > understood format. You could just write a simple CGI script for > your webserver that lets users read/write their whitelists.
I found a very dangerous tool that I have (I think) successfully beaten into safe submission. The tool is called "phpfm" ... a php File Manger. It allows you to browse through whatever parts of your directory structure you'd like, open and edit text files, etc.. Right out of the box, it was able to delete stuff, create directories, and all that - but I disabled most of that stuff in the configuration for it. It recognizes whether files are editable text by their extension. So it wasn't able to do anything with "autowhitelist" or "blacklist" or "incoming" files. So what I did was to create a different directory to be the root of phpfm's world. /home/kelvind/.tmda (normal TMDA directory) /home/kelvind/.tmda.phpfm (phpfm's root) Then I put symlinks into phpfm's root that pointed at the files I wanted to be able to edit. # ln -s /home/kelvind/.tmda/whitelist kdo.whitelist.txt # ln -s /home/anne/.tmda/whitelist amo.whitelist.txt # ln -s /home/kelvind/.tmda/blacklist kdo.blacklist.txt ...etc. Now I can simply login to this phpfm thing, and make whatever modifications are necessary. Good solution for someone with 100 users, including one's grandmother? No, I don't think so. But for folks like me who have to help manage TMDA for a half-dozen or so people, it has really proven to be quite handy. Oh, remember to change the GROUP of the files you want to edit to be the same group your webserver is in, then set the mode to 660. That keeps both TMDA and PHPFM happy. --KDO _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
