change keychain file location on dropbox

m w

Hi - I've had some fun moving the keychain file to a different location on dropbox.



I remember earlier versions of 1Password allowed to select a keychain file location directly from the preferences but the latest MAS version needs more convincing.



My starting point is that my keychain file is in ~/Dropbox/1Password/1Password.agilekeychain and my goal is to have it in ~/Dropbox/my-shared/1Password.agilekeychain.



So I move the keychain file from 1Password to my-shared and delete the 1Password folder. I start 1Password and it asks whether I'm a new user or used it before. I select the latter and select the keychain file in my-shared in the following dialogue. But when I check the file location under Preferences it shows that the keychain file is now under ~/Library/Containers/com.agilebits.onepassword-osx-helper/Data/Documents/1Password.agilekeychain. I click the button "Use Dropbox" and the keychain moves back to ~/Dropbox/1Password/1Password.agilekeychain; I'm just going round in circles...



I tried breaking the cycle by creating an alias (in Finder) of ~/Dropbox/my-shared and renaming it to ~/Dropbox/1Password but I get this error when I start 1Password:



[indent=1][font=courier new,courier,monospace]Failed to copy '~/Library/Containers/com.agilebits.onepassword-osx-helper/Data/Documents/1Password.agilekeychain' to '~/Dropbox/1Password/1Password.agilekeychain': Error Domain=NSCocoaErrorDomain Code=512 "“1Password.agilekeychain” couldn’t be copied to “1Password”." UserInfo=0x7fe4d4b27bf0 {NSSourceFilePathErrorKey=~/Library/Containers/com.agilebits.onepassword-osx-helper/Data/Documents/1Password.agilekeychain, NSUserStringVariant=(Copy), NSDestinationFilePath=~/Dropbox/1Password/1Password.agilekeychain, NSFilePath=~/Library/Containers/com.agilebits.onepassword-osx-helper/Data/Documents/1Password.agilekeychain, NSUnderlyingError=0x7fe4d47e8320 "The operation couldn’t be completed. Not a directory"}[/font][/indent]



However, creating a symbolic link in Termnial (ln -sn) works and the keychain file is now in ~/Dropbox/my-shared/1Password.agilekeychain and 1Password is happy using the file. But if I remove the symbolic link and start 1Password it asks me again whether I'm a new user or used it before ...



On the windows version of 1Password it just takes the file I select in the preferences; there is no "Use Dropbox" button. This seems to work at lot easier.



Is there a better way of telling 1Password where my keychain file is on dropbox?



Cheers

Michael

khad

1Password 3.9 adheres to Apple's application sandboxing guidelines. Therefore the only supported location of a data file for Dropbox syncing is the path to which 1Password moves your data when first enabling Dropbox syncing:



[color=#282828][font=helvetica, arial, sans-serif][CODE]~/Dropbox/1Password/1Password.agilekeychain[/CODE][/font][/color]



1Password for Windows is not sandboxed. (It is also a completely different app on a completely different platform.) Many things are different between OS X/Windows and MAS/non-MAS.



Sync is a big focus for us right now, so while I can't share any details or make any promises, I believe that what we are working on right now will make your life a bit easier. <img src='http://forum.agilebits.com/public/style_emoticons/<#EMO_DIR#>/smile.png' class='bbc_emoticon' alt=':)' />



Please let me know if there is anything else I can help with in the meantime.



Cheers!

m w

Thanks khad - up until yesterday my keychain file was in [color=#282828][font=helvetica, arial, sans-serif][i]~/Dropbox/my-shared[/i] but due to some other issue (using 1PasswordAnywhere) for which I contacted your support I had started playing around with the keychain file. I opened this topic in this forum because after the 1PasswordAnywhere was sorted I was left with the keychain file in [/font][/color][i][color=#282828][font=helvetica, arial, sans-serif]~/Dropbox/1Password[/font][/color][/i][color=#282828][font=helvetica, arial, sans-serif].[/font][/color]



[color=#282828][font=helvetica, arial, sans-serif]On my wife's iMac (same model as mine and same OS and app versions) the keychain is still at [/font][/color][i]~/Dropbox/b-shared[/i][font=helvetica, arial, sans-serif][color=#282828] (see attached). And this is without using a symbolic link. So it is possible to have the keychain in a different Dropbox location.[/color][/font]



[font=helvetica, arial, sans-serif][color=#282828]Maybe it works because it's been at this different location before the strict sandbox rules where implemented into 1Password?[/color][/font]



[color=#282828][font=helvetica, arial, sans-serif]Cheers[/font][/color]

[color=#282828][font=helvetica, arial, sans-serif]Michael[/font][/color]

khad

It is technically possible, but we do not recommend it. 1Password 3.9 can technically access:



[CODE]~/Dropbox/*[/CODE]



However, there have been many issues with certain configurations when deviating from the default location in 1Password 3.9 (especially when one starts throwing symlinks into the mix). For this reason we do not support anything but the default location in 1Password 3.9. If you have a need for a different path "temporarily" (i.e. until 1Password 4) you can email us a copy of your 1Password MAS receipt and we'll give you a 1Password 3.8 license key if you don't already have one. 1Password 3.8 is not sandboxed and has no such requirement.



I hope that helps. Please let me know. Cheers!

Cloaky

It would be awesome to be able to get rid of that file inside ~/Dropbox folder : )

No big deal, I know. I just like to keep things clean.

m w

[quote name='khad' timestamp='1348632045' post='62407']

If you have a need for a different path "temporarily" (i.e. until 1Password 4) you can email us a copy of your 1Password MAS receipt and we'll give you a 1Password 3.8 license key if you don't already have one. 1Password 3.8 is not sandboxed and has no such requirement.

[/quote]



Thanks khad - I'll keep that in mind in case I run into issues; so far it's been working fine and I'll await version 4 eagerly...

khad

Awesome! I hope you find it to be more than worth the wait.



Cheers,