<snip></snip> > I do however like the discussion that has been going on about content > filtering. I think all of that is very pertinent to the purposes of > the group. <snip>
I'm working on using squid as a transparent proxy. I have both a central machine and multiple personal machines. The multiple personal machine are the results of not having everyone agree on the screen resolution, base fonts, etc etc. As I work through setting up squid I'll take notes and pass on what I learn. Having a transparent proxy is key to being able to have a complete record. The current head scratcher I need to solve is having everyone passing through squid be required to signon to gain access. If any one has notes/howto on signon access control in squid please let me know. Setting a transparent proxy under suse requires changes outside of yast which can be a bit strange for those normally using yast to admin suse. I plan to do blacklists as well mostly as a learning exercise. Once I'm comfortable with my server the next step in my plan is moving to thin clients with a small central cluster. Between the family & grandkids I have a user base the size of a small office. My goal is to have 12 to 16 client workstations plus wireless support. I also need https/apache, samba over ssh (for the college kids), file sync tools, a robust back up server, and a cvs/subversion system. Is there anyone using sshd for inbound? I have a host.deny setup script I'd be happy to share. Have a great day oscar _______________________________________________ Ldsoss mailing list [email protected] http://lists.ldsoss.org/mailman/listinfo/ldsoss
