databoy2k

13 hours ago, Manish Chokwal said:

Hey @databoy2k & @Rado,

I appreciate you for being patient with us. Our team has tested it and found it working as expected. If possible, please share a short video of this issue so that we can investigate it better. Additionally, let me know if this issue occurs on other browsers as well and make sure the browser is up to date.

I've sent an e-mail to support@enpass.io with a video. The video shows some personal details that I would rather not share publicly, but can be shared within your team.

I just tried Microsoft Edge as well. The same thing happens. 

Both Edge and Chrome are up to date. The problem is in the Enpass Assistant.

As @Rado confirmed, it's when Enpass locks. So the steps to replicate, starting from a locked Enpass, are:

1) Go to any website and invoke the Enpass Assistant by right-clicking on a login field and clicking "Enpass"

2) Unlock Enpass via the Enpass Assistant

3) Make note of the credentials listed and the order of those credentials. Note that this is the same list of credentials that appears if you click the "Home" button of the Enpass Assistant. If you aren't experiencing the problem, click that "Home" button and make note of the credentials listed and their order.

4) Now, go into the main Enpass window and lock Enpass.

5) Go to a website that is NOT one of the credentials shown when you clicked the "Home" button, and invoke the Enpass Assistant by right-clicking on a login field and clicking "Enpass"

6) Unlock Enpass via the Enpass Assistant

7) The credentials list will show your correct website but then refresh the list as if you clicked "Home" and not the website that you just went to.

FWIW, I have to use the right-click to invoke Enpass. I've had nothing but headaches with the drop-down integration, so I've disabled that. But this is a bad bug that should be fixed as well.

I'm using Chrome 106 on Windows 10 with Enpass Extension v. 6.8.0 and Enpass 6.8.4(1166). Passwords are synced to a WebDAV server.

When I first open a web page, especially if it has been more than a few minutes since Enpass was last used (e.g. a reboot of the computer, or even just inactivity for more than about 10 minutes), use the context menu entry to enter passwords in a given login, and then enter my master password, Enpass often loads with the correct website but then reloads the assistant with my most used passwords but irrelevant to the current website.

So, for example, after a sufficent delay or reboot:

• Navigate to https://mail.yahoo.com (nowhere near one of my most common logins for Enpass)
• Right click on the username field and select Enpass
• Enter Master Password into Enpass Assistant to unlock Enpass
• For a second, I will see my Yahoo Mail credentials, BUT...
• Almost immediately afterwards, Enpass Assistant will reload and show all of my passwords sorted by decreasing frequency of use (currently Amazon, a filing website that I use for my work, a search website that I use for my work, my medical login information, and Lose It).

I am guessing that Enpass is performing a synchronization with the passwords stored on WebDAV, and once that synchronization is completed it reloads the Assistant. However, instead of reloading assistant to the same password originally chosen (in the example, Yahoo Mail) it's just reloading it to my database as a whole. It is as if once the Enpass Assistant reloads, it selects the "Home" button. You will replicate my experience by accessing a login page, right clicking, and then clicking the Home icon at the top left hand corner of the Enpass Assistant.

I think this started around 6.8 but I haven't been able to confirm.

I can take a video if it will help.

This is infuriating. Please fix by having reloads of the Enpass Assistant query the current website.

Beta is much better. Also seems to have fixed some issues with the Assistant not bothering to show the site's credentials and instead focusing on most used. So far no problems.

Definitely waiting on this fix. My phone and my PC may as well be on separate password lists at this point. Amy chance of rolling it out as a hotfix rather than waiting for a new version?

Hey everyone - here's an easy place to reproduce this bug: Google's products!

Go to Gmail. Open the sidebar where the calendar lives. Now try to add an appointment, or modify an existing one, or whatever. Especially if you invite someone to said appointment. You will be totally unable to use the sidebar. No cancelling, no saving, no nothing. Same issue in all Google products: drive, docs, sheets, etc.

Very frustrating. Please fix!

On a chromebook. I literally have to remote into Windows VMs to use the operating system. Chromebooks live with Enpass as an android app.

I really need to be able to start working with the webforms myself. I have a couple of complicated logins that Enpass is totally incompetent at filling in. Please get webform editing on the Android roadmap as soon as possible.

@Vikram Dabas Bug Report: latest version brought back the bizarre CPU usage. Past betas have been fine. Please let us know when the CPU Usage regression is fixed again!

On 6/4/2019 at 12:06 AM, djohannes said:

.. but just a question: My Chromebook has no fingerprint sensor, but there are Chromebooks coming with such a sensor (like the new Acers and the current Google Pixel Slate).. do you (or someone else) know if the fingerprint sensor is supported by Enpass on Chrome OS? And if not, would it be even possible to support it? 

@djohannes I'm pretty sure that I've seen a few times that the Android Runtime Container does not have access to the fingerprint sensor. Enpass certainly doesn't, and IIRC one of the other major password managers had this chat on Reddit. There's current neither access nor plans to give it. Probably a bug to star somewhere but I've never found it.

--EDIT-- Just received the update (6.1.0.225) and so far I don't seem to be having the CPU issues. I'll report if I do. I am having the same "Jumps up into focus when it locks" issue that we had in the past. Is that a demon that needs to be re-exorcised too?

Hi @Vikram Dabas. Thanks for taking the time to reply to my rant. You clearly sensed my frustration as I was wiping all things Enpass off my Slate and reinstalling the stable version. Thanks for getting the CPU Drain fix pushed out (to you and/or the team). I'm back in the beta boat.

It's tough - we're the ungrateful consumers constantly begging for updates and features while whining about costs. But then again especially beta testers are donating our devices (some of which are pretty high value) to you to make your product more marketable. It's a tough tension. I look forward to seeing how you guys resolve it.

In any event, I've grabbed the last two updates to the beta. Everything seems fast and fluid. There are two things that should still be looked at:

• I'm assuming that the Enpass Service notification will be mandatory; if that's the case, then please confirm. In any event, there's a typo in it: it reads "Enpass Autofill Serive"
• When the app has been running for a while and you go to close it, sometimes it keeps popping up as many as three times. Current setup causing it:
  • Running a Pixel Slate in Tablet Mode (no mouse/keyboard/cover attached) on Stable v74 (fully updated)
  • Enpass App is pinned to the shelf
  • Press and hold Enpass App and choose "Close"
  • Expected behaviour: Enpass App Closes
  • Experienced behaviour: Enpass App opens. Press and hold and choose Close, enpass app appears to minimize and re-open. Rinse and repeat until it finally does close (and it does, but after several tries

Those are the only ones that I've found so far. Thanks for improving the process for us.

Another random feedback that I'm going to leave here rather than risking trying to get it out elsewhere. I've had a horrible time getting this posted. I actually drafted the bulk of this the day that you posted (and @Dentonthebear) and couldn't actually post. The anti-spam filter kept advising me that I was posting too many times or that my browser was forbidden. I also keep getting login problems accusing my domain of being a spam domain. I am sending this from a static IP address because it's my business computer - I'm a lawyer in Canada. I'm not sure what's going on, but maybe the spam filter could be eased up a little bit? Thanks!

On 5/14/2019 at 10:27 AM, Dentonthebear said:

But this is a beta release, and as such as most other companies say are not necessarily ready for prime-time use.

I'm not sure if this was aimed at me or not, but I'll respond to it because I want to be clear that I wasn't whining about a beta product not being ready for prime-time use. Rather, I was complaining about the lack of updates to the beta. Whether those updates came in the form of an actual update to the software itself (even with a disclaimer of "Try this out and see if the CPU bug is gone") or in a post ("Just FYI: we've nailed the CPU bug and will be rolling out an update to the software in a fortnight, barring other build issues"), I just wanted to know that this was actually getting fixed and that we could expect to continue testing. 

As I said: I don't mind donating my bloody expensive device for testing beta products if I know that the testing is leading somewhere. I was starting to wonder if this was going to languish in beta for six months, maybe even a year. Over a month without any changes to the beta and no roadmap for when we should see it doesn't inspire me to help them beta test. It inspires me to wait in the rest of the forums for the update to hit whenever it hits and to not help them out with the test. If I'm alone in that sentiment, then so be it, but I wanted it said just in case there's others like me reporting everything from showstoppers to cosmetic bugs and then wondering if we'll ever see a fix.

So, I was right in on this beta until I started noticing my Pixel Slate getting hotter than Hades. Turns out the bug that was highlighted almost a month ago wherein Enpass consumes your entire device was still not fixed. There's the brutally obvious typo in the "Enpass service" that runs in the notifications menu (or, is it officially the "Enpass Serice"?), an entry which I assume is not going to be mandatory in the final release but has persisted throughout the beta. I've continued to have the "popup" issue that I reported back on April 9. I at least haven't seen any updates to the app or the extension since the first day (although maybe the extensions are being updated silently? I didn't record the version number when first installed). And there certainly hasn't been an update in this thread.

Would it be possible to get two things for those of us offering up our time and devices to help you guys beta test your software?

1. Regular updates to the beta software, perhaps monthly or bi-weekly, like most software that is considered "early release"? I'm thinking of, say, LineageOS/Cyanogenmod with even daily Jenkins builds for the truly bleeding edge stuff. We're probably here because we're comfortable with seeing things break and change, so we're also willing to help you guys test out those changes. We don't expect Beta 1 to go straight to RC overnight; hit us with a few more of these bug filled betas so that you can get lots of feedback on your fixes.
2. Updates in this thread as to if and when updates are coming out, what to look for, and just generally some transparency? Even just a post highlighting the different beta versions and changes between them for each of the app and the extension as a minimum, or identifying the changes in the next beta with a ballpark release date as a stretch goal, would go a long way towards exchanging some goodwill with us in this thread.

At this point, I've bowed out of the beta and gone back to stable. I can live with bugs, issues, even some instability from a beta. What I can't live with is problems without some indication that they are, or will be shortly, fixed when they're highlighted. I personally don't feel like my feedback and time is appreciated without either or both of my points above. I'm not asking you guys to open source your software, but if you're going to run a beta at least let us in on the actual development of that beta insofar as our feedback is concerned.

Depending on how long this beta takes to fix these issues or get to stable, I might end up having to revert back to Keepass or to another chromeos supporting service. Copying and pasting on the Slate without a keyboard is a complete pain in the arse that overcomes the ease of use with Enpass.

Hallelujah! Just signed into the Enpass forums using it. I've been going absolutely nuts trying to do this in the past on a Pixel Slate which, when no keyboard or mouse is attached, acts as a tablet and not a clamshell so the enpass interface took over the entire tablet and not just as a window. So far, so good.

One thing that I noticed: when Enpass locks due to inactivity after using it, the window pops back up (Clamshell mode for ChromeOS; haven't yet seen it do this on Tablet mode). Minor annoyance, but it literally interrupted me as I was typing this. Any way to stop it from popping up when it locks?

Given that we've never had a response to this from an Enpass team member, should we assume that ChromeOS support has been sunsetted?

There's lots of outdated links and old posts with respect to ChromeOS support, so I'm hoping that we can have an updated spot for all Enpass 6.X feature requests for ChromeOS. 

My wishlist is:

1. The return of autofilling support via the new Enpass Assistant in ChromeOS
2. Alternatively, a cleanup of the Enpass Keyboard support via the Android implementation in ChromeOS so that it actually works properly (for example, not making it take up the whole screen when you "tap to fill" and improving its access to what is on the screen)
3. Perhaps a new software keyboard for ChromeOS (not via Android) similar to the Keepass2Android implementation. That software uses a full sized keyboard when no login has been selected, but once you select a login it shrinks to a single small row with "user" "password" etc. as buttons that can be easily pushed.
4. Fingerprint support on the Pixel Slate and future ChromeOS devices with fingerprint scanners.

Any other things coming up? I for one would love an update on whether this is in active development or just on the potential roadmap.

Thanks team.

I came over from Keepass due to the keyfile support. However, the keyfile is absolutely a pain in the rear to use because it is 'forgotten' by Enpass and by the browser extension just like the master password.

Can there please be a toggled setting to "remember keyfile location", particularly in the autofill but also in Enpass, so that we only need to type in our password? The only reason why I use the keyfile is due to cloud storage, so on a local, regularly-used computer, I shouldn't need to go hunt it out each time.