AndyMac

Display issues: on Hi DPI screen (4k) set to 175% multiline titles are getting corrupted. See attached screen shot.

Just started to get a cloud sync error with OneDrive. Error 508503. What does this mean?

5 minutes later - Also disconnected and reconnected OneDrive and comes up with errors - variously 507503 and (from memory) 504503... it would be much more useful to have some description of the errors.

Another 5 minutes - it has now started working again.

An hour later error messages started again!

Just been trying out the new password generator - generally really good (together with the new tools to check if pawnd, etc. which I have already used to test my many passwords). A couple of comments/suggestions:

1. Maybe worth changing the setting "pronounceable" to be "pass phrase" as this is what is now is

2. When using passwords (i.e. not pronounceable) it is great to have ability to setup to ignore some symbols - this was needed

3. Would be also useful in the settings or the algorithm to have options to:

(a) not repeat the same symbol in a password and/or (at least) not have the same symbol duplicated next to each other

(b) not start a password with a symbol

(c) be able to set the minimum number of lowercase characters as well

4. Sometimes the generator creates a password it shows as "average" even when set to complex set of criteria (just limited set of symbols) with length of 12 or 14 - is this correct, could it not simply skip (or have the option to skip) these to guarantee a strong password?

14 hours ago, Anthony said:

I totally agree with this.

While I love beta testing, my password vault is too important for me for day-to-day use. I can't afford issues.

I was watching the v6 beta and liked the fact that it could run side-by-side with v5 as it was independent and ran its own upgraded database file. However, being forced into a beta scenario, which I on;y found myself because my phone app (Android) was upgraded this morning, is NOT OK.

You say you Love your users. Not giving them a choice is a very strange type of Love.

Same here - now I have my desktops all running 6 and my Windows 10 Mobile device unable to sync with any changes. If there is not going to be a version for Windows Phone/Windows 10 Mobile users (even a read-only version would be acceptable) that at the very least supports sync with the new version, then you need to allow users to stay on version 5! Alternatively, provide a way (even manual) to export/convert/import data across to the old version for Windows 10 Mobile users. One big reason I invested in Enpass was its support of Windows Phone/Windows 10 Mobile - and as a continued user of a Lumia 950XL (and probably continuing until support for the device stops later next year) I don't want to have to look for alternatives all over again!

Yes, I am one of the few still using a Windows 10 Mobile device - but there are a few of us still out there! and the (automatic) upgrade to Enpass 6 on my Windows 10 PCs seems to have broken the sync with the Windows10 Mobile app. Are you going to provide some level of support for Windows 10 Mobile users or are you simply discarding them with this release?

It would be REALLY useful to provide an on-screen notification if CAPS LOCK (and indeed NUM LOCK, if that is also possible) are active when typing the Master Password. If you have changed to CAPS (or NUM on a laptop keyboard, even though that is quite infrequent) it is not obvious when the Master Password you typed in fails, and some indication of status in the app on this screen would address this without compromising security.

When you select to use Windows Hello, it would be better if the application used this "by default" once started using the full key, rather than having to press the "hello" (smile) button to access this - or at least have the option to automatically use hello, allow use of hello, or not - maybe even better would be a selection of "Always use PIN, Always use Windows Hello, Allow use of Windows Hello, Always Use Full Pass Phrase".

Completely agree with this - and should be for any target cloud, so for OneDrive, DropBox, etc.

Just imported my existing data and see that tags do, indeed, replaced folders - with the model of Folder:SubFolder to offer nesting. Would like to see some way to find those entries with no tags attached.

Loving the new look, and the features or promised features. Looking forward to it moving to production. A couple of comments/questions:

I have used Folders extensively in Enpass (with multiple tiers) to manage a mass of information. There does not seem to be the Folders option in the first Beta.

Is this feature on the backlog, or is this feature being deprecated (which would be shame) or replaced with tags (which I'm not sure will do everything I need).

The one suggestion if folders are retained, that having some way to see which items are not in a defined folder would be a really useful feature.

I use Folders extensively and have hundreds of items in Enpass. It is difficult to find those cards that I have setup but have not got assigned to a folder. Having the option to switch on and off a folder in the list to show these unallocated items would be extremely useful - alternatively, having a feature to show unallocated items in a separate list and allowing them to be allocated to folders would be another approach that would help in these situations.

I would like to have more control over the password generator algorithm, both at a general level and, ideally, at a "card" level to cope with sites which limit what is and is not allowed. For example, having an Advanced set of recipe options as follows:

• Total Length, as current recipe
• Mix of types of letters:
  • Number of caps - between x and y (rather than just a fixed number) to make this more random
  • Number of digits - between x and y (rather than just a fixed number) to make this more random
  • Number of specials - between x and y (rather than just a fixed number) to make this more random
  • Min number of lower case letters, to work with rest of the recipe to balance out the mix
• An alternative approach for the above could be to just have a "minimum" number of letters in each case, with the randomising adjusting the numbers accordingly
• Control over which special characters are allowed in the recipe

Having the ability to control a recipe at a card level, or probably better still, to have a set of different recipes defined ("presets" which could be prepopulated with the option to edit/add/remove them) and then referred to by a card, would make the whole Password Generator function much more powerful.

Yes, it would be good to hear an update on this. Ideally supported by both the UWP app and the desktop app (maybe using the Desktop Bridge if that would provide the way for it to communicate with Edge).

Ok, I suspected that this may be the case. Maybe something to feed back to Microsoft in terms of their APIs...

Really waiting for the UWP version of Enpass to be able to do this as well - the Windows Hello integration and touch-friendly UI is really useful for me on some devices.

Loving the Widows Hello support in the Windows 10 UWP app - but would be even better if you had the option to be able to accept the Windows Hello logon (facial recognition/fingerprint) without having to press OK, so it became almost transparent for the user whilst still secure.