Jump to content

SirHaxalot

Members
  • Content Count

    4
  • Joined

  • Last visited

  • Days Won

    1

SirHaxalot last won the day on December 12 2018

SirHaxalot had the most liked content!

Community Reputation

2 Neutral

About SirHaxalot

  • Rank
    Newbie
  1. Yeah, this needs to be improved. It's by far the largest annoyance I have with Enpass. I think that the best solution would be that if you select Copy you will be prompted to save an entry with that password the next time you open the extension. Also, there really should be a "Add a new Login" button somewhere in the extension. The History feature is nice, but not very apparent... there are several times I wish that I would have known that it existed.
  2. Hello, Currently the browser extension doesn't really handle well attempting to login with a known login on an "unknown" website. Manually searching for a site and attempting to auto-fill instead causes the plugin to open the old unknown URL. This happens with Steam for instance, where the first domain for my login (steampowered.com) was saved for is different from the Single Sign-on domain (steamcommunity.com). Attempting to use my steam password by opening the plugin, searching for steam and clicking on it in the hope of auto-filling the form instead results in a new tab being opened with another sign-in site. First of all, manually searching for a password any attempting to sign in should fill the password on this site, although it would probably be good to have a warning here. Secondly, it would be nice if the plugin would offer to save the current domain to the login that was used to sing in trough auto-fill.
  3. Yea, the currently released versions is not in sync, which makes it impossible to use Cloud sync, possibly on all providers. The desktop version is currently saving to /Enpass/vault.enpassdbsync, but the Android app is still trying to sync to /Enpass6-Beta/vault.enpassdbsync That there is no way to change the filename doesn't help in the least.
  4. Currently there is kind of a pain adding Cloud sync to WebDAV targets. I need to not only know the WebDAV URL, but also exactly the path format that Enpass is expecting, which isn't clear at all. Should it be the root? Should it be the Enpass folder in the root? Should it be the specific backup file in the Enpass folder? The root WebDAV URL should be enough, the client should be intelligent enough to let me pick the database file from there, or browse and let me select the folder where the password database is synced.
×
×
  • Create New...