We are very grateful for your understanding as we deal with the inevitable mess from this incident. In the meantime, here are some resources that may be of help to you:

• Searching the Espionage Support Forum
• Espionage FAQ
• Espionage Manual: Choose “Espionage Help” from Espionage’s Help menu in Espionage (you can search it too!).

Many thanks for the understanding!

Greg Slepak
Tao Effect LLC

• NOTE: This update will cause the installer to run again (prompting you for your admin password)
• FIXED: removed “failed to get node path” console messages in ispyd.log on Lion
• FIXED: issue with application associations on Lion
• IMPROVED: removed some 10.5 dependencies. recompiled with llvm-gcc.

Bear with us, Lion turned out to cause some unexpected issues that weren’t caught in the 2.8.12 release, so this maintenance release is mainly for Lion compatibility.

As mentioned, this release no longer supports Mac OS 10.5 Leopard. If you need a Leopard compatible version of Espionage, please use version 2.8.10 instead.

Enjoy!

• NOTE: With Lion approaching, this will likely be the last release to support Mac OS 10.5 Leopard
• CHANGED: Removed ability to backup unlocked folders for integrity reasons (you can force it on an unlocked folder by holding the Option key when clicking on Espionage in the menubar)
• FIXED: “Folder is being backed up, please wait…” notification appearing inappropriately
• FIXED: “Backups Successful” notification appearing inappropriately
• FIXED: Update issue on Leopard
• IMPROVED: Updated documentation on corrupt database error

Two Important Announcements

Leopard support is going away

Apple is moving quickly and the changes that they have been adding to Lion are making it difficult to continue support Leopard. We want to make sure though that our customers have plenty of time to update to the latest and greatest operating system from Apple, which is why we make it a point to support the current OS and the previous OS. With the release of 2.8.11, we managed to release a version of Espionage that supports all three operating systems, but it was not easy. We would like to take advantage of some of the great new features coming in Lion, so, with Lion expected next month, this will likely to be the last version of Espionage to support Leopard.

Unlocked folders will no longer automatically backup

Removing a feature, especially a feature that is probably used by many, definitely requires justification, and so, here is why we are doing this:

Espionage’s backups uses a program called rsync to quickly backup only the changed items of an encrypted folder. It came to our attention recently that there was a small but nonetheless real possibility that a corrupt backup could be made if a folder was being backed up while its contents were being modified. Because rsync is not designed to handle this situation properly, we have temporarily disabled this feature to avoid the risk of creating corrupt backups.

HOWEVER! We have not completely disabled it.

Because the ability to backup folders while they’re unlocked is so useful, we’ve made it possible to do so via a little hidden shortcut until we can properly and safely handle the unlocked-folder backup situation ourselves:

1. Hold down the Option key and then click on the Espionage icon in the menu bar.
2. As you hover over the unlocked folders, you should see the “Backup Now” menu item appear on them.

You can then click on “Backup Now”, but only if you’re certain that the folder is not being accessed by any program, and make sure to not do anything with the folder until the backup is finished.

Enjoy!

• NEW: Lion support (now fully 64-bit!)
• NEW: Complete extended attributes support for the encrypted folder itself (xattrs on files inside the folder were always supported)
• NEW: Bitcoin application template
• IMPROVED: Custom folder icon support
• IMPROVED: Prevent unlocked folders from being backed up to ensure backup integrity
• IMPROVED: Updated documentation and added example with link to blog instructions for Microsoft Outlook
• FIXED: Espionage won’t complain if run from an external disk (or separate partition)
• FIXED: Helper failed to run if home folder is located on non-root drive (e.g. /Volumes/etc..)
• FIXED: Problems encrypting iPhoto Library
• FIXED: “Don’t have a record for it” messages wouldn’t go away (hopefully for real this time)
• FIXED: Alignment of master password field with written text above it
• FIXED: On folder restore, sparsebundles were incorrectly sent to the trash with a sparseimage file extension

Lion Support

It is recommended to update Espionage prior to upgrading to Lion. If you were not able to do this, no sweat, simply download a fresh copy from our website and replace your copy of Espionage with it.

Full Extended Attributes support

Extended attributes are pieces of data that can be attached to files and folders (metadata in a sense). Some applications on OS X use them for various purposes, like indicating that a folder should be displayed as a bundle in the Finder (iPhoto does this). Espionage now fully supports them on the encrypted folders themselves (extended attributes on files and folders *within* the encrypted folder have always been supported).

Enjoy!

An important maintenance update on the road to 2.9!

• NEW: Sparrow application template
• IMPROVED: SmartMove is now even smarter (detects change in parent folder location at lock/unlock).
• IMPROVED: Added documentation on how to recover from a corrupt database
• IMPROVED: Espionage can create folders that haven’t been created yet (but should be, like “Mail Downloads”)
• SECURITY: Remind user to secure-empty trash after changing the encryption on a folder
• FIXED: 2.8.8 broke Backup on Lock
• FIXED: “Don’t have a record for it” messages wouldn’t go away
• FIXED (2.8.10): Apps did not get associated properly in 2.8.9

SmartMove Improved

Espionage’s SmartMove feature gets an update in this version, making it more robust. Previously, Espionage was only able to track when the folder itself was moved, but would lose track of it if one of the parent folders were moved or renamed. Now, Espionage will sync up with the folder’s new location once the folder is locked or unlocked. All of the code related to moving and renaming folders has also been consolidated into one main class.

Enjoy!

Using Espionage With Microsoft Outlook

We’re happy to announce that with the release of Office 2011, Microsoft has fixed an issue that made encrypting Entourage data with Espionage difficult. Now, Entourage is replaced by a program called Outlook, and while there are technical reasons as to why we can’t include an application template for Outlook, you can encrypt Outlook’s data with Espionage. Below are the instructions:

Step 1 – Quit all open Office Programs and Microsoft Messenger

Before messing with an application’s data, make sure it’s not running!

Step 2 – Drag the “Microsoft User Data” folder onto Espionage

It’s located in:

/Users/[your username]/Documents/Microsoft User Data

Step 3 – Associate this folder with *all* Office applications

Microsoft’s applications can access each others data, and because of this it makes more sense to just encrypt the entire Microsoft User Data folder instead of attempting to isolate individual folders (you’re welcome to try encrypting more specific folders, just make sure to keep backups).

So, the next step is to locate the Microsoft Office folder and drag all the applications in it onto the box near the bottom. If you use Microsoft Messenger, associate that as well (that will also keep your chat logs secured):

Step 4 (Optional) – Keep the folder unlocked while logged in

Since so many applications are associated with this folder, you might want to just have the folder remain unlocked while you are logged into your user account. You can do this by checking the Autounlock At Login checkbox for the folder (in Espionage), and also disabling the Lock On Quit checkbox by editing the application associations on the folder. If you choose to do this, just make sure to enable your screensaver password (in Apple’s Security System Preferences).

That’s It!

Your Office data and emails are now encrypted.

Enjoy!

Espionage 2.8.6 is finally out, and it’s highly recommended as it fixes many important issues and adds plenty of polish:

• IMPROVED: Intelligence of application templates w.r.t. dependencies and more
• IMPROVED: “Choose Password” changes to “Password Required” when re-adding an encrypted folder to Espionage
• IMPROVED: Espionage now takes steps to resolve a situation when two disk images exist for one folder
• IMPROVED: Added documentation on ‘saved’ folders and other advanced preferences
• FIXED: “Lock Folder” contextual menu item not showing up
• FIXED: Handling of ‘saved’ folders. See new preference in Advanced preferences
• FIXED: Issue where device syncing could be disabled due to conflict with SyncServices
• FIXED: Size check is not necessary for already encrypted folders
• FIXED: Scroll bar wasn’t visible for the small association box when adding a folder to Espionage with too many associations
• FIXED: Unnecessary associations suggested when adding Mail folder(s) directly to Espionage instead of via the template
• FIXED: Hang that could occur if application association is launched independently during autounlock
• FIXED: Rare issue where user could be prompted for login keychain password despite using separate keychain
• FIXED (2.8.7): Previous version caused login keychain to lock if Espionage was set to use the login keychain
• FIXED (2.8.7): Corrected explanation in documentation for calculating folder capacity

Overview of Significant Changes

Advanced preference for handling “saved folders”

Some users reported getting excessive “saved folder” notifications, and this release includes a new advanced preference for fine tuning how Espionage handles this situation. Details are in the new documentation on the advanced preferences.

“Lock Folder” contextual menu revived

It turns out that in switching to launchd, we inadvertently broke the “Lock Folder” contextual menu on 10.6. This situation has now been rectified, and the way we’re doing it now means that new users don’t have to restart their computers after installing Espionage for it to become visible.

Other important bug fixes

The release includes other important bugfixes, including a rare and bizarre issue where iSync would disable itself, and a hang that could be triggered during the autounlock sequence.

In short, it’s an important release, and you can update your copy within Espionage by launching it and choosing “Check For Updates…” from the Espionage menu.

Enjoy!

Espionage 2.8.4 is out! Here are the changes:

• IMPROVED: SyncServices folder is now encrypted for many apps. Espionage tries to make sure it remains unlocked
• IMPROVED: The ‘Lock On Quit’ option is now per-folder instead of per-application
• IMPROVED: Relationship between ‘autounlock at login’ and ‘launch at login’
• IMPROVED: Miscellaneous improvements
• NEW (2.8.5): Added “Open Espionage” menu item to Espionage’s global menu
• FIXED (2.8.5): Rare minute-long hang when an app was launched immediately after another was unlocked
• IMPROVED (2.8.5): Added a warning regarding encrypting folders beginning with an underscore

‘Lock On Quit’ is now per-folder

Previously, when the ‘Lock On Quit’ checkbox was checked, it applied to all folders. In other words, if an application had two folders associated with it, it wasn’t possible to have only one of those folders lock when the application quit.

Now it is.

The “special” SyncServices folder

There’s a folder in OS X called SyncServices, located here:

/Users/[your username]/Library/Application Support/SyncServices

Any application that wants to have its data synced by OS X (whether through iTunes or possibly iSync), might have some of that data stored here. As this folder can be used by various applications, including ones that aren’t explicitly associated with the folder, it’s recommended to keep this folder unlocked the entire time you’re logged into your user account.

Most of the data in this folder is fairly non-important (for example, Mail keeps your email in a different folder, but some things, like Notes and account settings, can be stored in the SyncServices folder), and difficult to decipher, so it’s fine to leave it unlocked while you’re logged in. If you’re concerned you can turn on the screensaver password in OS X’s Security System Preferences pane.

You can encrypt this folder by dragging it onto Espionage, or by re-running the application template for Mail, Safari, iCal, or Address Book if you already have any one of them encrypted. Espionage is already setup to treat this folder differently so you don’t have to worry about making sure it autounlocks when you login.

(Note: All Espionage’d folders are instantly re-locked the second the computer loses power, or you logout or restart.)

Enjoy!

• NEW: Converted EspionageHelper to launchd agent, resulting in improvements to:
  • Improved security for non-enrypted folders (which are still obviously insecure)
  • Removes startup errors associated with Apple’s buggy Login Items code
  • Crash recovery
• NEW: iPhoto application template
• IMPROVED: Notification regarding moving or renaming unlocked encrypted folders.
• IMPROVED: Updated iCal template to reflect changes by Apple
• FIXED: Check to prevent encryption of Library folder
• FIXED: Rare situation where incorrect applications would be suggested as associations for a folder
• FIXED: SmartMove did not update app associations
• FIXED: Unnecessarily re-prompted for master password when stopping helper from preferences

Good-bye Login Items, Hello launchd

Up until this version, Espionage used OS X’s login items facility to start its helper program, which runs in the background and is responsible for bringing up the password prompt, unlocking folders, etc.

We chose this method because it was the only reliable way to have a program start at login on both Mac OS 10.5 (Leopard) and 10.4 (Tiger). It turned out, however, that Espionage was not compatible with 10.4 for various technical reasons, and we also noticed that in some rare cases, Apple’s code for putting something on the list of login items would break or flake out, so we’ve been eager to make the switch to what are called launchd agents, available in 10.5 and later, which act as super-powered login items.

Now, if Espionage’s helper crashes or is forcibly quit by the user incorrectly, it will immediately relaunch. This property enhances the “security” of unencrypted, password protected folders (which, don’t kid yourself, are still very much insecure, and are only useful for protecting relatively unimportant data from luddites).

There are other small benefits to switching to the agent system (and I won’t go into all of them), but needless to say, 2.8.3 is a rather significant update for a minor-point release, so updating to it is highly recommended!

Enjoy!

That isn’t the only change in 2.8 though, here’s the complete list:

• NEW: SmartMove – allows folders to be moved and renamed like normal, Espionage handles the details
• NEW: Espionage now handles importing previously lost encrypted folders when given their symlink
• NEW: Setting to prevent Time Machine from backing up a folder, available by right-clicking on a folder in the list.
• NEW: Prompt user for folder password during restoration in the event of issues retrieving it from keychain
• NEW: Remind user to enable Espionage’s backups if they’re not enabled.
• IMPROVED: Backups made safer: Espionage won’t overwrite backups with folders that failed to unlock
• IMPROVED: Better support for encrypting invisible folders (those that start with a dot)
• IMPROVED: “Lock Folder” CM on 10.6 now properly locks folder if used on folder’s mountpoint
• IMPROVED: Path Finder compatibility. Make sure to check Path Finder compatibility mode in the Preferences
• IMPROVED: Ensure Finder is active after a folder is unlocked
• FIXED: Issue with one of Espionage’s folder validation checks
• FIXED: Issue where Finder could cause prompt to appear immediately after a folder is locked
• IMPROVED (2.8.1): Minimized appearance of “Please lock” info alerts
• IMPROVED (2.8.1): Folders on Time Machine’s blacklist are removed from it when restored
• IMPROVED (2.8.1): Don’t allow non-encrypted folders to be added to Time Machine’s blacklist
• IMPROVED (2.8.1): Documentation for restoring from Time Machine backups
• FIXED (2.8.1): Problems importing invisible disk images
• FIXED (2.8.2): Rare issue where Espionage could hang on first-unlock of a folder because of Spotlight

Overview of Significant Changes

SmartMove

Previously, moving or renaming folders wasn’t very intuitive, and while we were aware of this, we weren’t sure whether there was a robust enough technical solution to make the whole process more inuitive.

I’m happy to say though that we finally figured it out and now moving or renaming protected folders is as simple as… moving or renaming folders!

I threw together a quick video showing off this feature:

Improved Time Machine Integration

Because Espionage moves a disk image each time a folder is locked or unlocked, Time Machine may end up backing up more than it needs to.

To ensure efficient backups with Time Machine, you can either make sure to run Time Machine when all folders are in the same locked state as they were during the previous backup, or, now with 2.8 you can prevent Time Machine from backing up a folder altogether (and use Espionage’s backups instead) for specific folders:

Stay tuned for more improvements in this area…

Updated Dropbox Instructions

We’ve also improved the instructions for using Espionage with Dropbox. The new-style setup lets Dropbox add its nice little badges on files and folders.

If you’re currently using the old-style setup and want to convert to the new way of encrypting Dropbox, it’s very simple:

1. Open Dropbox and go into its preferences.
2. Move the Dropbox to your home folder.
3. When it’s done, move the Dropbox again, this time select the *unlocked* Vault folder (in your Home folder, it will have a little arrow icon on it) as the destination.

Enjoy!