Jump to content
Enpass Discussion Forum

Leaderboard

Popular Content

Showing content with the highest reputation on 11/21/21 in all areas

  1. In no way did I defend the change. I pointed out it wasn't a bug. I said I understood why they made the change (which is not defending the decision, just acknowledging the reason they did it), and I very much criticized their handling of the rollout (suggesting how it could have been handled better), and I criticized their tone-deaf handling of the backlash (in the very next post after your criticism of the same). What I didn't do was make any personal attacks by saying things like "I couldn't possibly give less of a shit," and "wacko leftist crap," and "are you 5?" — none of which have anything to address the actual problem at hand. For the sake everyone else here — and the actual subject of this thread — I'm done with this conversation.
    2 points
  2. My point about that phrase was that saying "it's not a bug, it's a feature" sincerely indicates that a) the developers aren't understanding the problem, b) the developers aren't taking users' concerns seriously, and c) the developers are apparently unaware of the history of that phrase and how dismissive it reads. But the bigger problem remains that the developers didn't bother to explain this change at all. They apparently just expected users to discover their keyboard shortcuts don't work anymore, and then expected users to find their way to the shortcut settings, then set up their own new shortcuts. (Perhaps an easy matter for developers and techies, but not for the average Joe Websurfer.) It would have been a simple matter — and 1000% more user-friendly — to include a sentence on the "Enpass browser extension has been updated" tab that reads, "To make Enpass more compatible with the way most browsers handle keyboard shortcuts, users need to create their own new keyboard shortcuts for displaying Enpass and autofilling account information for this updated Enpass extension. Click here to create your Enpass shortcuts." With the "click" sentence linking to the browser's settings/shortcuts page. The fact that Enpass did not do this has led to all this confusion, and the assumption by users that this "feature" is a bug. How Enpass couldn't not have seen this coming is hard to imagine. What did they think would happen when, without explanation, an update broke a common keyboard shortcut?
    2 points
  3. It isn't turned on by default. You need to go into the browser plugin settings to turn that feature on if you want it. If you use Safari's password filling feature and Enpass you should only have one of those two turned on for inline filling, or they will get in each others way visually (just as it does for 1Password). Make sure the Enpass extension is enabled in Safari, then select the hamburger menu item on the bottom left: Select Settings from the popup menu that appears. Then click Browser Settings. Then click the Safari Browser button at the top of the window: This will open a new settings window as a tab in Safari. In that window, turn on the switch next to the Show Inline Autofill Popup Menu item: From then on you'll see an Enpass logo on login/password fields similar to the way you see a key if you have Safari's password filling feature turned on.
    2 points
  4. If anyone is wacko here it's you, not to mention being outrageously rude to the devs.
    1 point
  5. I think everyone claiming that the change wasn't publicized is being extremely sensational. I get the "years of [broken] muscle memory", but be honest.. you wouldn't have liked the change even if it had been clearly announced six months ago. You're (understandably) frustrated, but also trying to heap on unnecessary criticism to make a point of how evil Enpass is. Enpass is not the first, nor will be the last (software) company to make a change individuals don't like. Good companies make changes for the greater good of the entire customer base.
    1 point
  6. I think the "wacko leftist crap" was directed at me because I used the term "woke". (Apparently my political affiliation and my entire personal values in which I lead me life can be determined on a single word.) Anyways, I don't disagree with your comments. I actually found this thread because, I too, was confused by the change. I even agree with your (very articulate) explanations as to why the user base may be inconvenienced by having to train themselves a new keyboard command. My point was that I simply don't think it's worth getting raged up about (see #Jeetdoh's comments in this entire thread), as if this was a big conspiracy to undermine Enpass users. Life is too short, my friends.
    1 point
  7. Are you kidding me? You're trying to defend developers changing the PRIMARY WAY people trigger their application every day, multiple times per day, with zero notice and then not allowing people to set the actual setting back to our preferred method of triggering the application again with zero notice and then responding to user's justifiable anger with "it's a new feature, and not a bug"? And that's ok?!?! You're really trying to defend that? Are you 5?
    1 point
  8. You need to turn on synchronization of your chosen vault(s) and use the same service and location on both iOS and your desktop. (iCloud, Dropbox, NextCloud, etc.) or use WiFi synching and make sure both are on the same physical network and WiFi synching is enabled and active.
    1 point
  9. So, I left 1Password because of the BS that came with new "features", do I have to leave Enpass in my rearview too ? That's what I've honestly been wondering after reading the "it's not a bug, but a feature" reply. The intent behind the "feature" is nice and all, I can salute the initiative, the problem is three-fold in my case: As a result of the ability to customize my keybind across my multiple browsers/operating systems, I now cannot have my preferred keybind Said preferred keybind can still trigger the configuration window where I can't set my keybind because of said improvement No reply from the developer other than on this forum and the answer is "nope, sorry, not going to happen" when clearly the wrong solution has been used to remedy an issue, therefore creating new issues. At least an acknowledgment that this should be "investigated", "looked into" or simply discussed, I would have understood that. But just a plain "nope" was kind of reminiscent of AgileBit's way of not caring about what many customers may want vs what they thought we wanted. This, coupled with another issue I read in the forum, which is a bug I've had for months now, about the double click not working on the first attempt in the browser Extension, has led me to look for another password manager, again, such a shame. Edit: I almost forgot: So, you managed to bind Command with another key ? That's funny because any combination involving Command is invalid on my Macs.
    1 point
  10. 1. Press start. 2. Type “add or remove programs” and press enter. 3. Search for the msstore version. 4. Click unistall.
    1 point
  11. Not sure what change was introduced in the latest version, according to the change log, the browser inline autofill was added. However, the Windows Hello feature is finally working as it should have been on version 6.7.4 (934) on Windows 10. You will need to disable and re-enable Windows Hello authentication in the Enpass app to achieve this. Hope this will not be reversed in the future updates.
    1 point
  12. Hello Gulshan - Thank you for taking the time to reply. Just to clarify, I do understand the cloud is purely the storage medium and not involved in any encryption process, and why my suggestion was that the Enpass app folder, the vault and attachment files be randomly named, before being uploaded to the cloud. As you say, if a hacker gets access to the files, they would still require the master password. My thought is, if a hacker had no idea what the files were, in the first place, they are far more likely to be discarded or ignored. Currently, an Enpass app folder stands out, and its name tells the hacker the software used to create the files inside, making it more of a target. Thanks for your time.
    1 point
  13. Just wanted to chime in of support of this being a bug. In Enpass v5, searches were nearly instantaneous. Slow searching is something that has plagued Enpass v6 and has yet to be fixed. Enpass 6 broke a lot of things, but slow search seems to be one of the last lingering issues that never got prioritized to be fixed.
    0 points
×
×
  • Create New...