This is pretty obscure, but I thought I’d give it a shot…
I’m trying to mount a volume on an NT host. When I connect manually, the authentication goes through the MS UAM, which encrypts the password before it goes out to the server.
Apparently the server expects that afp connections be encrypted because…
mount volume "afp://" & fileUser & ":" & filePass & "@" & myFileServer & "/" & myFileVolume
just brings up the UAM password dialog. Oddly, smb mounts fine, but that’s of no use since I have to have it mounted through afp.
mount volume "smb://" & user_name & ":" & pass_word & "@server ip/volume name_1"
Does anyone know what mount volume is doing? Does it send passwords in cleartext?
I though maybe do shell script with mount_afp might work, but didn’t have any luck.
mount_afp "afp://;AUTH=Client%20Krb%20v2@myserver/myVolume" /Volumes/myVolume
Anyone have any ideas on this? I’m experiencing the same problem…
Are you using Jaguar?
Right now I’m working on a share mounting utility in AppleScript Studio for my university. Including the Samba password in the URI works perfectly under Panther, but in Jaguar, it does not, even in a test script. Sometimes it fails, other times it works.
A password that does work is an 8-character password consisting only of alpha and numeric characters. But I get an error when I use a password that is 12 characters and contains stuff like pounds, parentheses, ampersands, et cetera.
I’m going to do some testing later today to see whether the limitation is password length, character content or both. Again, under Panther, long passwords containing non-alphanumeric characters work fine when passed through the URI.
Okay, of the ten main Shift-characters (invoked through the numeric keys at the top of the keyboard), there are four which Jaguar does not support sending through a URI in AppleScript (probably through the Connect to Server window, too, but I haven’t tested that yet).
(ASCII character 35)
% (ASCII character 37)
@ (ASCII character 64)
^ (ASCII character 94)
It supports all the other ones just fine (!, $, &, *, (, ) ). I’m going to keep looking into this and see if there’s a way to send these character through.