configuration suggestions and browser lockdowns

[Kai Wüstermann]

Moin Bill!

Am Mittwoch, den 17.10.2007, 07:43 -0700 schrieb Bill Moseley:

> This does make management a bit more difficult, though, especially
> if the school decides to give out logins for each student using the
> machines (instead of, say, a "guest" login).
> 
> Can anyone offer suggestions how to best setup this configuration.
> Seems like NFS mounting /home, but I'm wondering what else can be
> shared to ease management.

You'll need a NIS-Domain, which hosts the usernames and passwords. Then
you mount /home via NFS.

If you have installed the same distribution on the machines, you could
use automatically updates, so would not have to do very much at the
machines, when they are working...

> Another question is how to lock down the machines.  I've looked at the
> Lockdown Editor Pessulus and Sabayon.  What about blocking URLs?  Mac
> OSX/Safari has a reasonably easy parenteral control where the browser
> won't go to any domain that isn't defined.  And when it's attempted
> the admin can enter their password to provide access.  Any pointers
> how to implement this?

This could do the proxy server squid with squid guard for you. If you
block the routing on the server, the browser has to lock on poxy server,
which can block the adresses you want to block. It also logs the access,
so you can check which user tried to access to a forbidden address.

Kai Wüstermann