[K12OSN] thin-client lock down

[Josiah Ritchie]

Each of these has "dot files" to configure the environment or a folder
holding the info. You could probably set permissions to read, but not
write for all that stuff and then give ownership to root. The ownership
is important, otherwise a slick student can change his access rights
back to write.

A simple script with the info you want should be able touch the files
(to make sure they are there) and then change the permissions for
/home/*/$configfile to simplify the mess of doing it by hand.

Maybe there is a better way?

JSR/

On Mon, 2004-08-23 at 10:41, norbert wrote:
> Hi,
> 
> We have been running a K12ltsp system for a year & have had great 
> results. One of the issues is how to lock-down the students desktop so 
> that they cannot make any changes to the menus, icons, or default home 
> page on the browser but still write to their home directory.
> 
> Ideas, suggestions are most appreciated as the project has thus far been 
> great, we've increased the number of teachers using computers from 3 to 29 !
> 
> thks
> norbert
> 
> 
> _______________________________________________
> K12OSN mailing list
> K12OSN at redhat.com
> https://www.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>
-- 
Josiah Ritchie
Network Administrator
Washington Bible College
Capital Bible Seminary