[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: get school connected to the inet



On Mon, Apr 23, 2001 at 12:40:16AM -0400, Robb Kidd wrote:
> Craig Sanders wrote:
> > a better idea is to have a teacher monitor what's happening with the
> > internet terminals while they're in use.
> 
> Would using a filter help if it were configured to alert a supervisor
> terminal on sites that would normally be blocked?  
> [...]
> Have the proxy log and alert, giving information about which terminal
> and user triggered a possible violation and why. If the supervisor sees
> that's it's Essex, disregard. 

that's part of what i meant by monitoring. part of it is keeping any eye
on the kids themselves, and part of it is keeping an eye on the squid
access logs. this is, of course, on top of trying to teach a class and
maintain order and all the rest of what a teacher does.

certainly, a script could be written to watch the squid access.log and
raise an alert with the responsible teacher.

the complete logs would still have to be analysed regularly because no
simple pattern match is every going to be able to detect all (or even a
significant fraction) of undesirable sites.

it's going to need a real live human checking the logs and randomly
visiting any suspicious looking URLs....and even that isn't going to
catch all rule violations.


the kids need to know that they're being monitored too - it only takes
a few being caught and disciplined for the rest to become a lot more
careful about how they use the internet. that doesn't mean that they all
cease doing questionable things - a smart kid will always be able to get
around any filtering or monitoring (IMO, if they're that smart then they
should be treated more like an adult anyway...actually one of the best
things to do with a kid like that is to get them to help with looking
after the system - if they can be trusted, that is).

craig

--
craig sanders <cas@taz.net.au>

      GnuPG Key: 1024D/CD5626F0 
Key fingerprint: 9674 7EE2 4AC6 F5EF 3C57  52C3 EC32 6810 CD56 26F0



Reply to: