You can change the creator type ... but you shouldn't. I am under the
impression that creator types are obsolete and that applications are
now identified by a UTI. And you shouldn't change that, either.
However, I see a bigger problem here. I have written an AppleScripted
application which is available as shareware. Within the application
bundle, in the Contents/Resources/ folder, there are two complete
application bundles. One of these is is copied to a location where
the user can launch it as necessary, while the other is run only by
the outer application.
The Parental Control restrictions you have described would seem to
interfere with my scheme. I have done little testing as a non-admin
user, and none with PC enabled, but I probably should do so.
This looks like something that a bug report should be filed against.
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?
