Thanks for this! It fixed the issue for me. For anyone who wants a quick script to make this change and open the IronKey quickly, follow my instructions. Please pardon my over-explanation. I did that for anyone who might need the extra info and/or context.
I wrote a script to enable the IronKey after entry.
Here's what I did:
1: Open a terminal
2: Type (in the terminal): ls -al /dev/rdisk*
You'll get back a listing that looks similar to this:
crw-r----- 1 root operator 1, 0 Sep 25 09:38 /dev/rdisk0
crw-r----- 1 root operator 1, 1 Sep 25 09:38 /dev/rdisk0s1
crw-r----- 1 root operator 1, 3 Sep 25 09:38 /dev/rdisk0s2
crw-r----- 1 root operator 1, 2 Sep 25 09:38 /dev/rdisk0s3
3: Insert your IronKey
4: Repeat step 2 (type ls -al /dev/rdisk*)
This time, you'll get a listing similar to the one you got last time, only there will be additional entries.
In my case, I had these additional entries:
crw-r--r-- 1 josh operator 1, 5 Sep 25 15:41 /dev/rdisk2
crw-r--r-- 1 root operator 1, 6 Sep 25 15:41 /dev/rdisk2s0
5: Those new entries, rdisk2 and rdisk2s0 represent my IronKey (note, you may have different filenames!). Also, for those of you unfamiliar with linux/Unix, "/dev/" is a folder on your system. The forward slash "/" just before dev means the root of your hard drive. The rdisk files reside in /dev/.
New rdisk files are created and removed as you insert or remove other hard drives (the Ironkey is a hard drive in this case).
6: Open a text editor and enter the following. Keep in mind that my entry, covering both the new rdisks - rdisk2 and rdisk2s0 are for my system. You may have different rdisk#'s. Change that part to fit your situation. Also, note that the * which follows the rdisk2* in my example means: Match all files named rdisk2*. That means that this will make a change to rdisk2 and rdisk2s0. If I had an rdisk2sblahdeblah, it would also match that.
Enter this text into your text file:
sudo chmod 644 /dev/rdisk2*
/Volumes/IronKey/IronKey.app/Contents/MacOS/IronKey
NOTE about those two lines:
The 'sudo' command means: Run the 'chmod' command with administrative priveledges. You can't run it without that. When this command executes, you'll have to type your OSX login password.
The 'chmod' command changes the permission of a file. In this case, you're granting read access to the rdisk files in question.
The '/Volumes/IronKey/IronKey.app/Contents/MacOS/IronKey' tells OSX to open the IronKey control panel.
7: Save the text file with any name you want. For this example, it is saved as ironkey.txt to your home folder. Once saved, close the text file.
8: Back in terminal, type the following commands (each line is a separate command followed by the enter key):
cd
mv ./ironkey.txt ./ironkey.sh
chmod 755 ironkey.sh
NOTE about these commands:
The 'cd' command will make sure you're in your home directory, where you saved the ironkey.txt file.
The 'mv ./ironkey.txt ./ironkey.sh' command will rename ironkey.txt to ironkey.sh. .sh means the file is a shell script.
The 'chmod 755 ironkey.sh' makes the ironkey.sh into an executable file. It'll be easier to run that way.
9: From now on (or until IronKey fixes this correctly), you'll do the following to access your ironkey:
a: insert your ironkey
b: open a terminal
c: type: ./ironkey.sh
d: type your OSX login password
e: Ironkey control panel will pop up and you can carry on as normal. Leave the terminal open or it'll lock your ironkey!
d: when finished with the ironkey, 'lock and quit' and you can close the terminal.