Espionage 3.0.1 Released!

IMPROVED: Ask for confirmation during setup assistant if user says “no” to launch at login

FIXED: Problem unlocking folders when master password is changed

FIXED: Allow encryption of folders inside Library

FIXED: Allow “Force remove from database…” when disk image is missing

FIXED: Allow passwords with non-ascii characters

FIXED: Problem unlocking folders when master password is changed

Note that it’s now possible to use Espionage to encrypt folders in ~/Library. Do this at your own risk and let me explain why: with Lion Apple introduced sandboxing which has caused a lot of headaches for many developers. It’s caused massive headaches for us, and was one of the changes that went into our decision to remove application associations. If you encrypt an application’s data with Espionage 3.0.1, there are some things to keep in mind:

Applications might store their data in the ~/Library/Application Support folder, but then if the developer enables sandboxing the operating system will move their data to ~/Library/Containers. If you had their data previously encrypted, this transition may not go smoothly, and even if it does, you might not be aware of it and suddenly the data is now unencrypted in a different location.

Because application associations are gone, you’ll need to unlock the application’s folder before using it. We’re considering our options as to what we can do here, whether it’s bring back application associations or something else, but don’t bet on it yet. The situation is hairy. In the meantime you can set the folder to auto-unlock when you login.

I just installed the update, and now I get “Internal error decrypting database, please see system log for details.” whenever I try to unlock it. How do I fix this? I’m running the latest version of Lion.