Re: eppc -> "Remote Access Not Allowed"?
Re: eppc -> "Remote Access Not Allowed"?
- Subject: Re: eppc -> "Remote Access Not Allowed"?
- From: Sander Tekelenburg <email@hidden>
- Date: Sat, 12 Jun 2004 00:29:51 +0200
At 14:53 -0400 UTC, on 2004-06-11, Graff wrote:
>
On Jun 11, 2004, at 11:05 AM, Sander Tekelenburg wrote:
[...]
>
> For some reason the eppc scheme chokes when the
>
> passphrase contains a hash ("#") character. Tsssk...
[...]
>
You probably need to URL-encode the password since it is being passed
>
by way of a URL:
>
<http://www.blooberry.com/indexdot/html/topics/urlencoding.htm>
>
>
Replace the hash (#) character with # and see if it works.
Indeed it does. Duh. Should've thought of that myself. Thanks! :)
[...]
>
This is not unique to the eppc scheme, it will probably occur with all
>
URLs. It most likely has nothing directly to do with Apple or
>
AppleScript.
Well, it most certainly has something to do with Apple, because when you
don't specify the username/passphrase in the URL, you get a dialog that asks
for that. That dialog happily accepts a hash and then happily chokes on it.
I can understand I'd need to encode this when providing the passphrase inside
the eppc URL in the script. But you don't always want to store passphrases in
scripts. It's often a security risk to do so. And for scripts that need to
work for different users, it's not even an option.
It seems unreasonable to me to expect users to type encoded passphrases into
pretty dialogs. The system should be smart enough to know that a hash needs
to be encoded and do just that. A hash in a passphrase doesn't give any
problems when using ssh or afp, so why should it be a problem with eppc?
--
Sander Tekelenburg, <
http://www.euronet.nl/~tekelenb/>
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.