Re: Tell Blocks Considered Harmful (was Re: open for access)
Re: Tell Blocks Considered Harmful (was Re: open for access)
- Subject: Re: Tell Blocks Considered Harmful (was Re: open for access)
- From: "John C. Welch" <email@hidden>
- Date: Wed, 10 Dec 2008 21:11:45 -0500
- Thread-topic: Tell Blocks Considered Harmful (was Re: open for access)
Title: Re: Tell Blocks Considered Harmful (was Re: open for access)
On 12/10/08 7:27 PM, "Chris Page" <email@hidden> wrote:
That's interesting, though it would have to require user interaction to authorize, since it's loading executable code from across the Internet. Would it still be useful if it required interactive authentication to run that script?
>From a security perspective, I think we might be better off requiring people to download and install that OSAX as they do today.
Honestly? Were Apple to be more...arsehelms about osax intruding on namespaces, a lot of this would go away. Just make the hierarchy:
OS wins over OS-supplied OSAX win over Applications win over third party OSAX. Always. Don’t be nice about it. Don’t even let conflicting OSAXen load.
When an OSAX loads, AppleScript should eval them, and if there’s a conflict that the OSAX loses, unload it, and kick out a dialog to the user. Make it easier when building OSAXen to at least check against OS and existing application namespaces. (you can’t test for EVERYTHING, but you can at least make it easier to check against standard OS and “standard” application namespaces.)
--
Politics:
A strife of interests masquerading as a contest of principles. The conduct of public affairs for private advantage.
Ambrose Bierce
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden