Some time ago I shared a free AppleScript interface I put together for accessing the Mac OS X keychain with some degree of speed and grace. The download, named “Usable Keychain Scripting” was my frustrated response to the more or less completely unusable Keychain Scripting interface in Mac OS X.
Usable Keychain Scripting was awesome, completely spanking Apple’s scripting support in speed and functionality. Frankly, I was hoping that by the time Leopard rolled around, they might have fixed the built-in scripting support, but unfortunately, they have not. So UKS still has a place in this world. As luck would have it, I don’t find myself particularly needing to script the keychain so often these days, but since I shared the resource in August, 2006, a few of you have gotten in the habit of using it. Some of you even wrote in to let me know that it was itself rather broken (and therefore unusable) as of Leopard. Thanks for the tip!
As I was addressing a confusing issue for Leopard (basically the keychain items all lost their “name” attributes), I also discovered something much more sinister. UKS was exceedingly unusable on Intel-based Macs, thanks to a classic “OSType < -> String” conversion problem, which didn’t account for byte order on Intel CPUs.
Long story short? If you’re one of the few who needs Usable Keychain Scripting, you’ll be a lot happier with the 1.0b3 release, which I’ve just posted.
If you’ve got an older version of UKS installed, be sure to get rid of it completely so it doesn’t get “addressed” when you write your script. To be sure, run the script:
version of app "Usable Keychain Scripting"
And make sure it’s 1.0b3. If it’s not, you’ll have to kill all off any running copy of UKS and throw out the old copy of the app. The safest bet is to throw away the old app and reboot your computer.
If you’re not one of the people already using it, keep it in mind the next time you get completely frustrated by how insanely unusable Apple’s keychain scripting is.