Salut Hilaire :) I am maintaining several computers at our school where I teach math and computer sciences (among others). Hence I could imagine those suggestions being a further improvement to squidguard with skolelinux. In order to start a discussion about their sense and feasability, I decided to make them public:
1) "Squid Guard Watch": To be warned right in time, in case of wrong additions, there could be a predefined vector of addresses that must / must not be accessable. Those vector could be checked automatically after each change of squid.conf / squid -k reconfigure, so errata can be detected at once. (This vector or rather matrix could include five "dirty" addresses and five "white" pages. 2) Allow different rule sets for different machines (teachers' pupils' machines), for different times (morning / evening classes / lunch break), for different classes (below / above 18). 3) Allow easy editing of those pages that report unallowed access (on our old server, I used different background colours, red for "dirty" pages). Alternatively / Additionally those pages could be localized by browser settings. 4) Possibly, have a separate form to select allowed filetypes (.exe, .zip., .mp3, ...) - maybe combined with max filesize. Please don't get me wrong: I am quite aware, that getting squidguard to run out of the box is quite pretentious an aim to achieve. My suggestions are rather meant to provike some further ideas and discussions - and open discussions are a pro for our concept, I feel. Regards Ralf
