Re: limiting website useage
Jeff Kinz <jkinz@...
2006-02-01 15:44:20 GMT
On Wed, Feb 01, 2006 at 10:38:03AM -0500, Joe Auerbach wrote:
> I suspect, given the number of schools using ltsp, that I'm not the
> first one to need to do this, but here goes.
> We are implementing ltsp on a much larger scale here at work and the
> collectors (I work at a collection agency) will need net access to go to
> various skiptracing sites (white pages, yellow pages, etc) but we'd like
> to prevent them from going to any other sites (you know . . . THOSE
> sites, but I think the idea is to have an allow list rather than a block
> list and to just assume that sites are blocked by default).
> How have some of you set this up? It would be easier if every user had
> their own /etc/hosts file, i think, but they all share one. And I want
> to limit them individually (so the legal department, for example, has
> broader access than the collectors).
Use a proxy like squid. has all the flexibility and power you need, is
fast and efficient. the hosts file idea is just not a good idea.
Maintaining it will prove to be very labor intensive and its vulnerable
to more attacks from individuals within your company.
Oh, and limit the lawyers to only the pest extermination sites...
Jeff Kinz, Emergent Research, Hudson, MA.
speech recognition software may have been used to create this e-mail
"The greatest dangers to liberty lurk in insidious encroachment by men
of zeal, well-meaning but without understanding." - Brandeis
To think contrary to one's era is heroism. But to speak against it is
madness. -- Eugene Ionesco
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
For additional LTSP help, try #ltsp channel on irc.freenode.net