MAC OS X Mountain Lion Ironkey Temporary Fix

Posted by Darrin on September 26th, 2012


For all those that are waiting on IronKey to get a fix together so you can access your IronKeys again, I have put together the steps I used to get this working.

  1. Before inserting your IronKey, Open a Terminal window
  2. Type the following command in the terminal window and note the output:
    ls -l /dev/rdisk*
  3. This should give you output similar to the following:
  4. Insert your IronKey and run the above ls command again. You should see additional /dev/rdisk* entries. In my case it was /dev/rdisk4 and /dev/rdisk4s0
  5. Using the above information, modify the following script to use your /dev/rdisk4s0 entry. Note that you will need to change the <username> to your username that you are logged in with. Then save it in your home directory as (or whatever you want to call it).

    # Updates and loads the IronKey interface
    sudo chown <username> /dev/rdisk4s0
    /Volumes/IronKey/ &
  6. Update the permissions on the script so that it can be executed.chmod +x

Now when you insert your IronKey open a terminal and execute to update the device and allow the IronKey app to access the device.

I am sure there is a way to load this script each time the IronKey is inserted. But will have a look at that later.

For those that are adventurous and do not want to put in their password each time they run the above script. Using the visudo command add the following line to the bottom of the sudoers file. If you don’t know what this file does DO NOT TRY THIS, this may screw with your system in bad ways if you get it wrong, or cause other hazardous things to happen or open security holes…

<username> ALL=(root) /usr/sbin/chown <username> /dev/rdisk4s0

I am sure there are others out there that have some ideas/input, please let us know so we can get this sorted for everyone suffering from this issue.

How to disable SSL and redirect to port 8333 VMWare Server 2.0

Posted by Darrin on September 20th, 2012

This article describes how to disable SSL protocol and redirect to port 8333 in VMware Server 2.0 in Linux

By default there are two ways in order to log-in to the VMware console; either using SSL connection (port 8333) or without it (port 8222). However logging without SSL is only allowed from a localhost on which wmvare server is being installed. Every connection attempt from a remote host to the VMware console on port 8222 (http://hostname:8222/ui) will end up with redirection to SSL channel on port 8333 (https://hostname:8333/ui).

read more at How to disable SSL and redirect to port 8333 VMWare Server 2.0.

Restore hidden files with Apple Mac OS X Time Machine | Me in IT

Posted by Darrin on September 10th, 2012

Apples Time Machine works great, but restoring hidden files that start with a dot, like .ssh, .bashrc or .Trash is difficult, but possible!

Time machine uses the settings as used by the Finder. So first step is to change Finders behaviour, to show hidden files. Execute this command as a regular user from within the Terminal. more …

Restore hidden files with Apple Mac OS X Time Machine | Me in IT.

Setting timezone in CentOS, RHEL, Fedora

Posted by Darrin on May 17th, 2009