Mathias Brodala

Thanks for all the pointers. Interestingly the upgrade went smoothly with my 2nd user account, even `xdg -open enpassauth://dropbox/` worked without any additional work.

However, this didn't work on my main account but I found a solution by simply manually invoking Enpass:

/opt/enpass/Enpass "enpassauth://dropbox?state=security_token_sinew&code=<code>"

All arguments (state and code) are shown in the browser URL when trying to set up Dropbox sync.

With this I could set up Dropbox sync successfully.

After upgrading Enpass to version 6.0 on my desktop (Xfce, Debian Sid) today, I was greeted with a wizard to restore my wallet. I went and selected Dropbox and after logging in and giving Enpass permissions I was greeted with a site prompting me to launch `xdg-open` which in turn gave me the following error message:

Quote

The address "enpassauth://dropbox/?state=security_token_sinev&code=..." could not be opened.

The given location is not supported.

(Freely translated from German)

How should I set up sync from Dropbox with Enpass 6?

@Akash Vyas, what about Linux? Do you use password input widgets provided by the toolkit here?

I just stumbled over this. Are there plans to properly fix this? Maybe Keybase can change their login form to support Enpass here?

@Hemant Kumar, ah sorry I didn't mention this. I'm using Xfce and its panel "xfce4-panel" which provides a systray plugin out of the box. My distro of choice is Debian.

Here are a few of my applications which have the behavior I'm used to:

• Pidgin
• Exaile
• Thunderbird (via FireTray add-on)

It would be neat if Enpass would not only reveal itself when clicking the tray icon once but also hide itself on another single click. That's the usual tray icon behavior of all kind of desktop apps on Linux.

Currently clicking the tray icon when Enpass is visible simply does nothing aside from focusing the window.

@Ankur Gupta, sounds great. I assume one should join the beta program to have a look at this alpha?

On 6.4.2016 at 9:00 AM, Ankur Gupta said:

Hello Mathias, Like you we are also very concerned and working on ways to have maximum protection against data corruption.
Although Enpass itself uses SQLCipher to store information in widely tested and secure database but I agree that in a worst case scenario, data file might get corrupted during cloud’s (Dropbox, iCloud etc) own syncing operation.
At the moment, there is no check for corruption before uploading keychain to cloud but internally in our lab we do have a tool to check for data corruption and fix the affected items. Now it has almost been tested on pilot database here and we are planning it to add into main stream code. In coming releases for desktop we are also adding feature of auto-backup to strengthen the data safety against loss and corruption.

For safer side, we always recommend to take manual backups at regular intervals. Keep posting such nice suggestions and check-points to keep us on our toes.

Regards
Ankur

Hi Ankur,

thanks for the insights. How would that auto-backup look like exactly? Would Enpass simply create copies of the database at regular intervals?

I'll add the database file to my regular backup for safety. ;-)

Regards,
Mathias

Does Enpass ensure that a corrupted database is not synced to the cloud?

I want to be sure what happens in the worst case and if my database is corrupted somehow having that broken database synced to the cloud and thus overwrite a good version would be really bad. Since I can only sync to one cloud provider I'd have no way back in this case.