Sharing Vault on local network using 1Panywhere

saschinger

In my little office (4 people) there's one developer working on a linux computer. With the others I'm sharing a special vault already, local-folder sync is working fine with them.

But to integrate our linux-fellow, I wonder if we can user the html-file (1PasswordAnywhere) to share this vault with him on our local network. How to do that?

Since Apple has disabled the webserver-sharing-function from OSX, there's no chance to access a file via http/s locally. Has anyone experience in syncing the html-file on a local network?

Ben

Hi @saschinger‌

Unfortunately such a setup is beyond the realm that we can support, but I have a couple thoughts and ideas I can share.

1PasswordAnywhere should work fine for read-only access to the shared 1Password data file. It does not allow for changes to be made to the data file. If the Linux user needs to be able to make changes, they could try running 1Password in a Windows virtual machine or emulated in WINE (or other similar setup). They would need a 1Password for Windows license to do so, of course.

There may no longer be web server software shipped with the non-server version of OS X, but the server version I do believe still comes with it, and also there are 3rd party web server packages available for OS X.

Really for this situation though our official recommendation would be to sync with Dropbox. We cannot guarantee the stability of the type of setup you've described, and our ability to troubleshoot it would be limited.

Thanks!

Ben

saschinger

Hi, thank you for your good advice. So running 1P (WIN version) on WINE is working on Linux? I think virtualising Windows only for this is a kind of overhead.

One more suggestino: If our Linux fellow only needs read-access, would it be possible to sync a special folder between our Macs and a local NAS, so that he could access the html-file provided by the NAS webserver?

Ben

In answer to both of your questions: again it isn't a solution we'd support, but I've heard success stories from other customers who have done it. :)

Thanks.

Ben

saschinger

Hi ben,

thank you again.

So the linux guy will only get read-only, which is no problem.

We will try to sync & share our common vault first on a NAS. If that is not working, we try second on a Mac with server capabilities.

We will not use ownCloud because it's officially not supported.

I just wonder, how to deal with the items that are already "conflicted" (sadly I had already tried to sync my personal vault using owncloud and now I have a few items with names like "0C0C9E83E3ED4609AEA8989D9F02D94E_conflict-20140319-145303.1password" inside /data/default). Maybe just move this vault back to Dropbox to re-activate Dropbox-Sync for the vault and rename this item to 0C0C9E83E3ED4609AEA8989D9F02D94E.1password?

Ben

thank you again.

You are very welcome.

So the linux guy will only get read-only, which is no problem.

Correct, unless he wants to try 1Password for Windows.

I just wonder, how to deal with the items that are already "conflicted" (sadly I had already tried to sync my personal vault using owncloud and now I have a few items with names like "0C0C9E83E3ED4609AEA8989D9F02D94E_conflict-20140319-145303.1password" inside /data/default).

Unless the data in 1Password is incorrect, these items can be ignored.

Maybe just move this vault back to Dropbox to re-activate Dropbox-Sync for the vault

If Dropbox is an option it would be a great solution here. It would allow your Linux colleague to use 1PasswordAnywhere and would get you on a supported sync platform.

Thanks!

Ben