Alex Gurenko

5 hours ago, Kay Lin said:

As I have been ignored by the officials in these months, I'm extremely disappointed and upset about the about Enpass. I bought Enpass on all of my devices and this is the kind of service I received. I've already switched to another service that is open source and it works on ARM devices. I will no longer recommend Enpass to others because of this and the switch to subscription-based licensing. Goodbye.

 Well, calm down, we're not 12 here. It's weird how people are saying that they leave Enpass due to new subscription-based licensing, while MOST of other password managers always had this model and still have it now. It's everyone's choice whether or not to continue using products or look for alternatives. That's exactly why I was waiting for a reply, so I can make a decision.

@Pratyush Sharma thanks for the information, appreciate it.

So, it's been a few months. @Anshu kumar any chance you can comment on this feature request? Is it coming, should we look around for other solutions? I must say, I've switched to Pinebook Pro (aarch64) as my primary laptop outside of work and I'm really missing a password manager there.

On 8/29/2019 at 12:44 PM, Anshu kumar said:

Hey @Scibex,

Thanks for writing in.

Currently, we don't have any immediate plans to add support on Raspberry Pi. However, I've forwarded it to the concerned team for further consideration.

Thanks!

With a rising popularity of Pine64 products (Pinebook[ Pro], PineTab, PinePhone) I would forsee more people wanting to use Enpass on ARM-based linux machines, are you guys ready to re-visit ARM support in 2020?

It seems like changelog for linux version is also at 6.2.0, so "version 6.3.3" below linux download link is very misleading. In any case something needs to be fixed

It looks like yum repository is seriously out of date. I'm running Fedora 31 and latest available version is stuck at 6.2.0 for a long time now.

Here is an output from dnf.

dnf --showduplicates list enpass

Installed Packages
enpass.x86_64                                                         6.2.0.537-1                                                          @enpass
Available Packages
enpass.x86_64                                                         6.0.0.197-1                                                          enpass
enpass.x86_64                                                         6.0.0.214-1                                                          enpass
enpass.x86_64                                                         6.0.0.218-1                                                          enpass
enpass.x86_64                                                         6.0.0.228-1                                                          enpass
enpass.x86_64                                                         6.0.0.230-1                                                          enpass
enpass.x86_64                                                         6.0.1.239-1                                                          enpass
enpass.x86_64                                                         6.0.3.263-1                                                          enpass
enpass.x86_64                                                         6.0.4.281-1                                                          enpass
enpass.x86_64                                                         6.0.6.323-1                                                          enpass
enpass.x86_64                                                         6.1.0.407-1                                                          enpass
enpass.x86_64                                                         6.1.1.451-1                                                          enpass
enpass.x86_64                                                         6.2.0.537-1                                                          enpass

I've re-downloaded repo file before trying to make sure I have correct repo in use.

My wife have this problem both on Windows and Android; Mine are working fine since Linux version is still 6.2 but Android is 6.3. Looks like Windows version corrupts TOTP?

With latest update of Enpass Firefox extention, the build-in manager stopped working and does not filling or even suggesting already saved login/passwords. I've tried and after removal of the extension - functionality restores. I would really like to have control over this behaviour if that's expected.

I'm running Fedora 30 KDE and Firefox 69/70

Hm, I've removed the extension, closed browser and installed it again, seems to be working now.

10 hours ago, Lox_ said:

Same issue here (Chrome and Firefox). I was also wondering if there is also an extension update ?

Settings->Browser->Review Browsers is empty.

As a side note, I am a developer and Linux server administrator, ask me anything technical to help you find the issue.

Ubuntu 18.10 (Gnome Shell)
Enpass 6.0.0 (214)
Firefox Extension 6.0.0.56b
Chrome Extension  6.0.0.56

@Vinod Kumar I actually have two machines, both have authenticated browser, but on one machine it works, on another it still shows error and extension does not work.

$ lsof -i:10391
COMMAND  PID     USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
Enpass  5261 <username>   30u  IPv4  41930      0t0  TCP *:10391 (LISTEN)

I'm using Firefox 63.0.3 installed from official Fedora repos (@updates)

9 minutes ago, Anshu kumar said:

Hey @Lox_

Sorry for the late reply and inconvenience caused to you.

We have fixed some browser extension related issues and just pushed a new update. So please update the app and share your findings.

Thanks!

Same issue, is there an extension update that comes with a new app version?

6 hours ago, Lox_ said:

Even support@enpass.io won't reply

I've started to have same issues yesterday that you posted above. With no configuration changes to the systems where I use Enpass.

@Anshu kumar Do you guys have a bug tracker to see what's already have been reported and what are you working on? Honestly, I find that Enpass 6 is barely usable in a day-to-day operations right now on Linux, at least for me and I'm not sure what's the best format to report all these things. I see that worst things are obviously reported here, but still there are things here and there, that makes it very-very difficult to use and some are just concerning.

3 hours ago, Anshu kumar said:

Hey guys,

I would like to share that Last Synchronized and Last Attempt are two different timings. Last Synchronized is the time when the actual syncing of data took place last time and the file was updated on the cloud, while the Last Attempt refers to the time when Enpass looked for any changes in data on server (and maybe it didn't find anything to sync and is not matching with Last Synchronized). This is why you see different time stamps for both.

Cheers!

May be you want to consider the name change for these parameters since it keeps getting people confused?

7 hours ago, Andy Long said:

I first want to say thanks for the hard work on Enpass 6. It really looks good and latest beta runs much better than in the past (especially on Android!) Don't know if this is the best place to post this but I looked around and didn't see a similar problem. I have the latest Enpass beta installed on Kubuntu 18.10. Sync with Google drive works initally when its authorized through browser. But subsequent requests fail. Attached is a screenshot that shows it was originally synced at 4:46 this afternoon with last attempt a few seconds ago. Am I the first to ask about this? I haven't tried it with OneDrive or another cloud yet. Nor have I tried it on another Distro. Not that big a deal. I'll keep on using it. If I know I have to sync something new, I'll just disconnect and reconnect. But want to report it anyway.

Yeah, this is to me looks like a confusing part and I'm not sure if the wording is really good. The "Last Synchronized" field shows when was the last time data was changed and synced TO the device. "Last Attempt" - shows when the data was last time checked for relevance. So, if you DID change data in the cloud and press Sync Now, both field will match, if you DIDN'T change anything in the cloud and press Sync Now then Last Attempt will update, but Last Sync will be at previous value.

On 11/29/2018 at 1:47 PM, wolfyrion said:

 

I fixed my problem by using KDE Window Rules

 

What rules you've set?

1 hour ago, Tadly said:

Here are some more issues I'd like to report/discuss:

3. Browser extension should ALWAYS focus search.
If you: open the extension -> select an entry -> close the extension -> open the extension, the search field is not focused meaning you can't just start typing

I can second that too, it was also annoying in Enpass 5.x, also I've noticed on occasion when clicking start button in Fedora KDE brings Enpass 6 menu, until closed and opened again. Keyboard shortcut (Super Key) works as expected. Can find a pattern when it happens, so far seems random.

Same for the scrolling issue, also I'd like to mention that I'm missing Minimize on start option, I don't really like a window pop up on start, I'd rather it ask for the password/pin when the first attempt to access the vault is made (like the 5.x version did).

No sigfaults that I've observed.

I'm running Fedora 28 KDE Spin

P.S. Thanks for the repos, this makes life so much easier

1 hour ago, Vikram Dabas said:

  Hi @Alex Gurenko

We've already received a lot of feedback regarding the authentication with other browsers like Firefox, and our dev team is working on it.

Also, we thought to pick the Google accounts from the device and ask user to choose one, as done in Enpass 5. But the issue would be with the multiple vaults where to set up Google sync for secondry vaults user had to unnecessarily add the accounts in the device first. 

Okay, fair enough. Basically if it will eventually work with Firefox browser, I don't have strong preference. Actually maybe even better for custom roms too

 So, as previously mentioned, authentication with Google Drive does not work with Firefox and better question is, why do you use browser re-direct, rather than system function to authenticate with Google?

On 12/5/2017 at 1:30 PM, Akash Vyas said:

Hey @Alex Gurenko

One of our users had the same issue and he reported that he fixed the issue by installing "compat-openssl10-devel". So, for now, please try the same and let us know if it helps. We'll be looking for a fix on our end.

Cheers!  

This package actually exists, but conflicts with openssl-devel package in Fedora.

On 11/17/2017 at 9:09 AM, Anshu kumar said:

Hi @Peter Wang

The final version of the Firefox 57 extension is already up and can be downloaded from our website.

Cheers! 

Are you planning to push this extension to addons.mozilla.org ? It's been a while since FF 57 is released and the working addon exists, but keeping on a separate web-site is kind of going against the idea that web-extensions introduced.

The Download section specifies that version 5.6.5 is the latest for linux (including changelog), but it still downloads version 5.6.0 (Enpass_Installer_5.6.0)

7 hours ago, Akash Vyas said:

Hey @Alex Gurenko

Please let me know the version of Linux OS you're using and the path of the Enpass installation directory. 

Thanks for your co-operation.

Hi, I'm using Fedora 27 KDE spin and Enpass is installed in ~/Enpass

I want to create a separate tracker for the problem described in other topic. Currently update check does not work on at least versions 5.5.6, 5.5.9 and 5.6 via EnpassMaintenanceTool with following error:

URL Scheme not supported: https (https://dl.sinew.in/linux/packages)

On 9/2/2017 at 1:58 AM, niemalsnever said:

Great that the new WebExtension is finally in beta/available for public testing. I'd advise you to link to this thread in the thread on Firefox 57+ compatibility in the Browser Extension forum.

This is in my opinion a bad idea, because it means that the Enpass WebExtension would not be synced with Firefox Sync, which means users would have to download the extension on all their devices manually, which is, frankly, a bit uncomfortable.

Enpass Beta v5.5.9 seems to be released on the beta PPA for (Ubuntu/)Linux as well, and also connects beautifully with the Firefox WebExtension (tested on Linux Mint 18.2, with Firefox Nightly 57.0a1 and Enpass Beta v5.5.9.

That's great it's released on beta PPA, but I'm on RPM-based distro, so other means to install would be appreciated =) As for for the WebExtension, I would hope it's only for beta-testing purposes and once passed will be uploaded to Mozilla's Add-ons.