Jump to content
Enpass Discussion Forum

Damasta

Members
  • Posts

    55
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by Damasta

  1. My setup: Surface Book 2, Windows 17763.195, all updates (Firmware etc.) installed. Enpass 6.0.0 (218) syncs to OneDrive, connected to three other devices. After a restart, Enpass requires me to enter my master password once despite Windows Hello being enabled in the settings. Hello seems to work from then on. Please fix! Dom
  2. This was a different thread that was closed - due to "windows wont let us do this". In fact, you are incorrect and have been at least since Windows 10 Version 1709. For proof, please see the app "Ear Trumpet", which is a brilliant volume control app that replaces the windows built-in volume control. It totally opens and minimizes back to the system tray. It auto-starts on boot. In fact, I think Enpass should work just like it. @Akash: Please revisit your answer to that closed thread? Please stop using Windows as an excuse why things don't work. ;-)
  3. 6 Months later and still no Windows Hello or decent touch support on the bridge version... Why not just cave in and dev plugins and extensions that connect to the local vault file and/or the cloud? I don't see the need to connect the extension to Enpass app.
  4. Sorry Akash, that answer doesn't even come close to it. 1. The UWP version is... Universal. It works on PC, Phone and HoloLens and always looks and feels the same. The w32 Bridge/Desktop version doesn't. 2. The UWP version is great for touchscreens, the w32 Bridge/Desktop version is from the stone-age and is horrible for touch screens. 3. The UWP version supports Windows Hello biometric (un-)lock with fingerprint, face, iris and soon with palmvein recognition. Forget your password - literally! 4. The UWP version does not support browser extensions. IMHO that is a bad excuse tho… I don't see why a browser extension can't just connect to my cloud or local vault file and extract passwords from there. I understand that the UWP model will not allow apps to communicate directly to localhost - which, from a security standpoint - is a good thing. But if the UWP can connect to a cloud or a local vault file, why can't a browser extension? Other extensions certainly do... Do I sound like a bitter UWP user? Absolutely. I've tried both versions and I'll rather have the UWP version any time - hands down. Check the store - the UWP version even has better reviews, too.
×
×
  • Create New...