Jump to content

databoy2k

Members
  • Content Count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral

About databoy2k

  • Rank
    Newbie
  1. databoy2k

    ChromeOS Support - Enpass 6.X

    Given that we've never had a response to this from an Enpass team member, should we assume that ChromeOS support has been sunsetted?
  2. 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: The return of autofilling support via the new Enpass Assistant in ChromeOS 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) 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. 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.
  3. 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.
×