In the coming days, 1PasswordAnywhere (the 1Password.html file within your Agile Keychain folder) will stop working for 1Password data stored in Dropbox.
Logging into my Dropbox account, it looks like this day has already arrived.
Those were the 3 main use cases for 1PasswordAnywhere when we designed it and each one has a better alternative available today.
Hopefully in 2016 you no longer need 1PasswordAnywhere.
First, you can continue to use 1PasswordAnywhere with an Agile Keychain stored locally or on a USB drive. Many browsers restrict access to local files, however, so be sure to configure your browser to allow local file access. Just be aware that this could potentially pose a security risk.
You can get around local file restrictions in Safari by selecting Develop > Disable Local File Restrictions from the menu bar. (You will need to enable the Develop menu first if you haven’t already. This is done by checking the box for “Show Develop menu in menu bar” on the Advanced pane in Safari’s preference.)
In my view, these instructions should be in the HTML file itself, kind of like Apple did with the HFS wrapper.
Also note the recent change in the “Lock on sleep” behavior:
Previously we had it set to auto-lock when the computer itself slept; a recent update made it so it auto-locked when the display slept because that’s what most people expected from the app. (I suspect that most people think a laptop goes to sleep as soon as their display does. It’s too bad Apple got rid of the little “breathing light” indicators on its MacBooks!)
That explains why it started prompting for my password every time I returned to my Mac. I always sleep the display but leave it running.
Stay up-to-date by subscribing to the Comments RSS Feed for this post.