On Feb 8, 2008 11:04 AM, Gregory Hodges <[EMAIL PROTECTED]> wrote: > one of the Tech Specialist that had worked here in the past had managed > to get Camino to look like Firefox. His reasoning was that way the kids > would think they were using Firefox and look up the wrong hacks
What do you mean by "hacks"? Skinning Camino is not going to provide any real security benefits (if someone is actively trying to break local security, figuring out that they aren't actually using Firefox is going to be trivial); instead you should identify specifically what you don't want people to be able to do and prevent those things directly. > the problem is that the Camino that we are using is old 1.0.2 to be exact > and is not playing well with some of the web sites that we use. The > problem with the new Camino build is that the "about:config" offers a > way for the students to enter their own proxies negating our proxy > server. First off, about:config was present in 1.0.x as well, so presumably you had a solution in place before. What were you doing to prevent changes to proxy settings in that version? > Is there a way that we can either disable that command or hide > it so that the students can not access it. Assuming the students have write access to their home directories, they can change preferences by editing their profile directly, so hiding about:config isn't actually what you want. Instead you'd want to lock the all of the proxy settings. http://kb.mozillazine.org/Locking_preferences explains how to lock preferences in Firefox; we've never actually tried it with Camino, but there's a good chance it would work there as well (however, note the "Caveats" section of that page). If you try that, I'd be interested to know whether or not it works. -Stuart _______________________________________________ Camino mailing list Camino@mozdev.org https://www.mozdev.org/mailman/listinfo/camino
