Re: Trouble with Remote Apple Events (eppc) and Keychain
Re: Trouble with Remote Apple Events (eppc) and Keychain
- Subject: Re: Trouble with Remote Apple Events (eppc) and Keychain
- From: Maximilian Schirmer <email@hidden>
- Date: Wed, 10 Oct 2007 00:22:05 +0200
I recommend filing a bug report with Apple (noting that not all
users seem to be affected) and hope they identify the cause and get
some fixes in pronto. In the meantime, the only workaround I can
suggest is to avoid the AEM auto-authenticating by adding the
remote host's username and password to the eppc URL yourself. The
Keychain API docs are at: <http://developer.apple.com/documentation/
Security/Reference/keychainservices/index.html>; I believe there
are third-party ObjC-based wrappers around as well but don't know
anything about them.
I will file the report and include the findings from the dis-
cussion here.
Bypassing the authentication system manually was an idea I
already came up with, too. I implemented it, including keychain
handling and dialogs to for authentication -- it is working fine.
But when users enter a wrong login/password combination, the
UserNotificationCenter.app is launched and presents an authentication
dialog. Entering the authentication data to this dialog will lead
to the corrupted protocol identifier when saved to the keychain on
Intel machines. This basically kills the idea of bypassing the
system.
The problem is the sequence of events: the authentication dialog
comes up BEFORE my call to [remoteiTunes performMessage:@"..."]
returns... the return value would indicate wrong authentication, but
I can only react with my own authentication dialog AFTER the
system's dialog has been completed (which triggers the bug)
or canceled.
The system's authentication dialog blocks the execution of my
application's code until it has been closed.
I've got a couple of uncommon ideas how to go further this way,
messing with the system's dialog until it no longer pops up...
but I've got a bad feeling about it. For all intents and purposes,
I would rather use the system's authentication handling.
So I will file the bug and wait until it is fixed, my application
is a small freeware tool. It's my own amusement that keeps me
messing with this defect.
p.s. Somewhat OT, but since you mentioned you're working in ObjC/
Cocoa you might like to take a look at objc-appscript <http://
appscript.sourceforge.net/objc-appscript.html> as a much more
elegant native alternative to all that ugly mucking about with
NSAppleScripts.
Thanks for the suggestion, Appscript looks promising. I'm currently
using my improved version of Stefan Mueller's "APAppleScriptHandler",
"ABFRemoteAppleScriptHandler", but I will definitely give AppScript
a try.
Thank you all very much for your help so far!
Max.
--
trying to make things work... without serendipity in my life
(Paradise Lost - Pray Nightfall)
_______________________________________________
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