I’ve been using my Mooltipass for a while now, so I figured it was time to do an update on what I think of it, now the initial excitement of a new toy has worn off.
I have to admit that I have not fully migrated to using it. This is for a number of reasons, the first and foremost being that the toolset for using the Mooltipass is currently limited. I am unable to easily add arbitrary credentials to the device, and the integration support is limited to the Chrome extension.
This means that for a lot of the uses I have, as I don’t live my entire life online, I have to use the python command line tools to add credentials, which I have yet to get working on Mac OSX. Also, to use the Mooltipass to authenticate me, I have to use the device menu to find the credential set that I require and use the keyboard emulation to input to the computer.
Those are the negatives. I am using the Mooltipass every day and moving more and more of my accounts over to using the Mooltipass for authentication. I currently use the Mooltipass between two laptop and two desktop computers, giving me access to Windows, Linux and Mac OSX to test it on. I also have been using it for a couple of iDevices. It works seamlessly on all machines, the only slight frustration being that I have to input the PIN every time I change machines. Compared to remembering complex passwords though, I guess this is nothing.
Since I first got the Mooltipas, there have been a number of software and firmware updates which have solved a number of the issues I began having and have made life with my Mooltipass considerably more comfortable. The lead developer, Mattieu Stephan (AKA Limpkin) has been very quick to respond to any bugs or feature requests that I, or anyone else provided and I have had an updated firmware for my device within half an hour for one issue.
In order to attempt to aid Mooltipass integration, I started an attempt to create a cross platform native Mooltipass access library using libusb however unfortunately I haven’t had an awful lot of time to get this working and mostly just have an interface design for the library. My hope is to get simple credential requests working, then integrate it as a proof of concept with the lock screen I’m using under linux, slock or, alternatively, the login manager slim.
I have been carrying my Mooltipass with me daily and I have found that the best way to do this is to use a cheap airform case originally designed for Nintendo DS. The Mooltipass fits almost perfectly in the case, with space to the side for a USB cable, and the case I have has a net pocket, I assume designed for transporting games and spare styluses (styli?) but is very useful for storing smart cards, if you do not mind carrying the card along with the device.
Finally, I got a colleague that happened to have a laser cutter to cut me out one of the holders for the Mooltipass, so it now sits on my desk in a way that I can easily see it when it flashes at me. It was cut in MDF which actually made the Mooltipass slide around on it a bit, but after I had painted it, the friction of the paint made it better at holding the Mooltipass.
Overall, I’ve had a very positive experience with the Mooltipass. There’s still quite a lot still needed to make it a painless experience and can easily solve all my password/authentication problems, but I can see that happening soon. I have been recommending the Mooltipass to everyone I can, I think it’s a great device. Personally, I feel the price is a little high at the moment, but I understand that this is the case with builds that have to run in such small batches so I’m not sure what could be done to reduce the cost.