I've been playing around with Parental Controls just to see how they
work. I've been getting logically inconsistent results which makes me
think that there are some serious problems with PC that need to be
fixed.
But, I did find one interesting capability. You can install
applications into the users applications folder (./Users/<username>/
Applications/). These applications don't show up in the list of
applications in Finder & System Configure, but they can be used if
either:
1. Uncheck - This user can only use these applications
2. Check - This user can only use these applications and
check some applications in the Applications list.
I had some trouble getting this to work and these results are not
guarenteed. Nevertheless, you may want to experiment with this.
Conclusion. Parental Controls are more trouble that they are worth -
don't become a parent.
On Jun 10, 2007, at 2:18 AM, Antonino Petriliggieri wrote:
While working on a project for a medium organization that wants osx
macs deployed with non-admin rights and limited access to
applications I needed to authorize 3 applescript droplet, but
Parental Control let me add just one.
The problem is that all applescript apps have the same creator type
and "only" this specific information is used for listing authorized
apps. Of course any application has, in general, a unique creator
type, but the same limitation applies to copies or different
versions of the same application.
This is in my opinion a serious limitation in usage of Parental
Control in business environment.
There is any alternative to change the creator type of each droplet
to solve the problem?
