RE: Avoiding A System Events Password
RE: Avoiding A System Events Password
- Subject: RE: Avoiding A System Events Password
- From: Scott Babcock <email@hidden>
- Date: Fri, 14 May 2010 01:10:47 +0000
- Thread-topic: Avoiding A System Events Password
You absolutely need administrator privileges to enable accessibility, because the setting is represented by a semaphore file named ".AccessibilityAPIEnabled" in /private/var/db. The file needs to be owned by 'root' in the 'wheel' group (uid 0, gid 0). However, System Preferences is apparently able to use the fact that you're an admin user to gain the elevation of privilege to create the file with the correct ownership, without requiring you to enter credentials. A non-admin user would need to enter credentials to alter this setting in System Preferences.
-----Original Message-----
Date: Thu, 13 May 2010 16:17:54 -0500
From: Luther Fuller <email@hidden>
Subject: Re: Avoiding A System Events Password
To: AppleScript-Users Mail Mail <email@hidden>
Message-ID: <email@hidden>
Content-Type: text/plain; charset="us-ascii"
On May 13, 2010, at 3:27 PM, Bill Cheeseman wrote:
> On May 13, 2010, at 12:53 PM, Luther Fuller wrote:
>
>> System Events always asks for a user password
>> when changing UI elements enabled .
>>
>> There is no reason for System Events to require a password, since the user can make the change manually without one. This is very annoying!
>>
>> Does anyone know a way around this problem?
>
>
> I'm surprised that the Universal Access pane of System Preferences does not ask for a password. I discussed the System Events password issue with Apple several years ago, and Apple was adamant that enabling access for assistive devices presents a security issue. I used to disagree with Apple's position, but I don't any longer.
I think I will just stay with my current script. It seems that I'm the only user who will be using it.
I had intended writing a scripted application that would simply replace an emlx file in the Finder with a pdf copy. Using "CUPS-PDF" helped reduce the UI scripting to just two lines of code, which is an improvement.
The problem with "CUPS-PDF" is that it uses a configuration file ("cups-pdf.conf") which is user modifiable. If the user modifies the location where pdf files are printed (default = /private/var/spool/cups-pdf/username/), my script breaks. I have looked at the "cups-pdf.conf" file and think it a bad idea to modify it via a script. I've searched, but I can't find any info on the format of .conf files.
The ideal solution would be a unix command or a Scripting Addition that would simply print a document window (in Mail) to a pdf file which is named and located in the script without installing a virtual printer. AFAIK, no such thing exists.
_______________________________________________
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