rlengland

Backing up the vault when a change is made is fine but 60 retained versions is a bit high for me.  I think the ability to set a limit on the number of backup files would be a great option.

Also, deleting backups older than some number of months would be very good.

On 12/31/2018 at 12:17 PM, rlengland said:

For the record, I have Enpass running and syncing using Dropbox on the following devices

HTC One M9  phone Android 7.0 release 4.27.531.6
Enpass vers 6.0.4.196

Fedora Linux v29 Kernel 4.20.5
Enpass vers 6.0.4(281)

Linux Mint v18.3 Kernel 4.15.0
Enpass vers 6.0.4(218)

Yes. I have a legacy system that is 32 bit. Upgrading is impossible due to hardware limitations. This means that upgrading  Enpass is not possible and that seems to make it impossible to sync between the 32 and 64 bit systems.

There are a lot of legacy systems still in use.

Is this a permanent situation or will 32 bit support be provided in the future?

I am finding this to be a problem as well.  I have a Linux Mint 19 (Tara)  32 installation and it appears that there is no 32 bit support. Not updates and the version on "sinew" is only for 64 bit systems.

Is this a permanent situation or will 32 bit support be provided in the future?

Just as soon as you post, you find out that if you update Enpass to v5.6.5 everything works.
Sorry for the wasted bandwidth but perhaps this will help someone else.

The plugin is failing to work on my system:
Fedora 27, Firefox 57.01,   Enpass 5.6.0,    Plugin v 5.5.2

Image attached, "Enpass Connection Error"

Is there a solution for this?  Is anyone else encountering this?

Is there a new plugin for Fedora 27 / Firefox 57 besides the beta I've seen referenced? The plugin reports v  5.5.2

I am using Firefox 57 on Fedora 27  Enpass 5.6.0

The Firefox plugin gives the same Connection error discussed by n8v8

I have found that on Fedora  (24 and 25) the update 'tool' or 'option' does not function but if you perform a new install it will pick up all the configurations that were in place for the previous version. At least this happened going from v5.3.0 to v5.4.1. 

It was necessary to install the new version in a new location since the installer detected the existence of the previous location and was not able to over-write it. 

If we aren't going to see and RPM (yum or, preferably, dnf) installation option then allowing the installer to over-write the old version (after warning this is happening) would be a very helpful change.

Appreciate the tool, keep up the good work.

Unfortunately, I'm running Fedora and CentOS so that won't help.  I did see the earlier posting about Debian and wanted to put in vote for "the other side".

Thank you for responding, and please think about expanding the 32 bit version coverage.

Is there any chance that a 32 bit version for Linux can be built?  There are a lot of legacy systems that see long lives after being taken off Windows. Many of these are in the hands of those who could use all the security help they can get.