Jump to content

wmc

Members
  • Content Count

    15
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by wmc

  1. wmc

    Please Withdraw Version 6

    There are too many universally experienced bugs for a small support / development team to chase in an organized fashion that will not result in a much degraded product that will be much harder to maintain and upgrade going forward. Many of the bugs create security issues (e.g. the failure of Enpass browser extensions to block access to web login sites until the Enpass master password is entered, then subsequent failure to load the info from the vault for the page with the login controls (UID, password). A number of bugs impact stored data integrity and reliability. E.g., browser extensions seem to "forget" Enpass has been installed and working fine in with a particular "Master Password" in the past, and reports it has not completed set-up, needs a master password to be created, or previous data restored. However, despite selecting auto-backup creation in version 6, no backups get created, and attempts to restore from the local computer lead to a Google login page. (?!?) Further, the database form, format and location used to store the "vault" has changed from v 5 so that the process of "rolling back" will be tedious with many manual actions required by the user while understanding it is highly likely that v5 will not be able to use a v6 vault for its data. Version 6 install / uninstall make a mess of the Windows registry leaving multiple entries with duplicate information that is incorrect. For example, after installing v 6.0.2 the registry contains no entries referencing this version but does have entries referencing the previously installed 6.0.1 (239) referenced as 6.1.239.0. There are multiple keys in HKCR that contain the exact same info. HKCR\.enpass_card should reference one of the subsequent classes in HKCR from its "OpenWithProgids" key, but there are at least EIGHT OTHER Progids in HKCR all for same "@{SinewSoftwareSystems.EnpassPasswordManager_6.1.239.0_x86__fwdy0m65qb6h2?ms-resource:...". Thus the uninstaller needs to be fixed so that it cleans up all the entries it leaves behind when the software is uninstalled since this splattering of multiple keys with duplicate data may be at the source of some worsening issues each time a new v6 install / uninstall / re-install is attempted. Although I haven't attempted it, I believe this shotgun blast of Enpass version 6 registry entries left behind after its uninstall will make a rollback to version 5 problematic especially for Windows users not versed in registry editing and the subtleties of changes in Enpass database form, format and location. For these reasons the Enpass development team needs to withdraw all version 6 releases and provide A FULLY TESTED UTILITY TO COMPLETELY REMOVE TRACES OF VERSION 6 FROM THE REGISTRY / SYSTEM FILE STORES, AND CONVERT THE V 6 DATABASE BACK TO A VERSION 5 COMPATIBLE "WALLET" SO USER CAN THEN SUCCESSFULLY RE-INSTALL AND OPERATE WITH VERSION 5. This will then give the developers and Enpas QC engineers time to re-engineer v6 from top to bottom with REAL unit testing AND REAL THOROUGH in-house use case testing BEFORE releasing to beta testing or the "stable release" channel.
  2. wmc

    Please Withdraw Version 6

    It appears that you (GeoLuz and tox1c90) are in the "exception" rather than "rule" category for Enpass v6. It also appears you are primarily Edge and smartphone users of Enpass, both of which are incredibly castrated environments compared to the full-function desktop experience we have with Enpass v5 in full-function browsers like Firefox, Safari, Chrome on a desktop. As for compatibility issues, if version 5 ran reliably and flawlessly, then as soon as v6 installed by Enpass's auto update and completely blew up (extension can't reliably connect with the application, can't find the data store, and when it does hook up, can't auto-invoke the credentials for the log-in page you have invoked - the most basic reliable function of version 5) then the onus is on Sinew Software, NOT users, to fix the problems. The sheer volume of problems indicate this was an update to please Enpass, and the fancy Windows messaging version (so Microsoft can insert itself into your machine security situation and try to force you into OneDrive client-hood). There was apparently no or little attention paid to impacts of design and coding changes to the "Traditional" version and interfaces with non-Microsoft extensions. The fact that Sinew Software remains silent, provides no updates to address all these issues and no help to those they apparently ignored in the beta test / release cycle indicates that their roadmap is a Microsoft / Edge / Window phone / OneDrive centered plan so that users of non-Microsoft browsers can just fall to the wayside, live with the problems or find other products that actually work with non-Microsoft browsers and cloud services. The Sinew Software silence, their lack of effort to address these issues is the coward's way out - they should just tell Firefox, non-MS cloud service users etc. that they will no longer support these browsers / services and make a clean break with those users who have been forced back to version 5 with all the SERIOUS functionality and reliability downgrades the auto-update to version 6 inflicted upon them. But I'm happy that those who are enamored of Edge and OneDrive, Microsoft Store app versions etc. have a product that works for them. It is still no help for the rest of us who swallowed the Sinew Software "good will" based on experience through version 5 on other browsers.
  3. You may not have scrolled low enough on the page for downloading older versions (https://www.enpass.io/support/where-can-i-download-older-version-of-enpass/) There are listings for the rev 5.x versions of extensions for Firefox, Chrome and Safari. As mentioned above, there is no way to rollback Edge since its extension comes exclusively from the Microsoft Store and they only support the "latest" version absent Sinew Software withdrawing Versions 6.x from release.
  4. My Post of Jan 5 is not entirely correct. You CAN DOWNGRADE, but with caveats: Windows 10 Edge Browser cannot be rolled back (you would have to do that through the Microsoft Store, and it is not equipped for roll-backs). You have to disable auto-update of the Enpass desktop application. You have to disable auto-update of browser extensions. (I found a way to do that in Firefox, but not in Chrome) otherwise the browsers will update the extensions to 6.x.x and not be able to hook-up with the desktop application. I've been running with the versions from the link posted by gargolito since about Jan 8. Nice to have the old Enpass functionality back. BTW, if you are in mind to rollback then perhaps you are also of the opinion that Sinew Software should withdraw the Enpass 6 releases to start the design, develop, test, release cycle over with a more organized, better managed development and test cycle (at least) before re-releasing v6 to beta testing. If so, please at your vote to the thread, Please Withdraw Version 6 at
  5. wmc

    Please Withdraw Version 6

    Go to the downloads page. Near the bottom in smaller type find the link in the line, Looking for an older version of Enpass? Get it from here. That will take you to instructions for downloading the last working version 5.x.x application and extensions. NOTE: you need to follow instructions carefully for the Chrome extension install. And in Firefox you have to, on the "Add-ons Manager" tab (from the "Tools->Add-ons" menu) click on Enpass, and in the resulting pane disable auto-update or it will put you right back at version 6 for the extension. Note also, there appears no way to downgrade the extension in Edge since it relies on Microsoft Store, just one more indication that Sinew Software should withdraw version 6, including extensions available in various vendors app stores. BTW, the Enpass 6 data file is not backward compatible with Enpass 5 and I know of no conversion tool to make it so. However, one thing Enpass 6 appears to have gotten right is that it renamed your last Enpass 5 file "walletx.db.backup" when it replaced it with the "vault.enpassdb" file buried deeper in your Enpass documents folder.
  6. You can. On the downloads page there is a link near the bottom of the page to older versions. You have to download the application, and the extensions separately. You have to remove the Enpass 6 extensions from your browsers (NOTE: Special instructions for installing from .zip package in Chrome, no option to downgrade Edge). In Firefox after removing the 6.0.x extension and installing the Firefox extension from the .xpi file you have to click the Enpass entry in the add-ons list, and disable auto-update or it will put the 6.0 extension back right away. I haven't figured out how to disable auto-update of the extension in Chrome yet. But I've been running with the "downgrade" to Enpass 5 for almost a week with no issues. Enpass 6 uses a totally different format (and file location) to store your data, and AFAIK there is no utility to convert you data from an Enpass 6 to Enpass 5 format. If you have added items since upgrading to 6, you would need to add them again when you "downgrade". The most recent Enpass 5 compatible data file will appear in your documents\Enpass folder as walletx.db.backup. It appears to be a file made when Enpass 6 initially gets installed. Rename (a copy of, to be safe) the file to "walletx.db" and you have the most recent Enpass 5 data ready to go. The next step should probably be to start looking for a PM from some other source. It appears Sinew Software is not about to do the right thing - withdraw Enpass 6.0, re-work it properly from the ground up following proper software design, development and test processes before releasing back to beta testing. So going forward it will just get buggier as more band-aids spit and bailing wire get applied trying to reactively respond to all the bug reports with little ad-hoc patches.
  7. wmc

    Please Withdraw Version 6

    As a former software engineer, technical lead and software architect for major aerospace software systems, I know a thing or two about what happens when proper design, development test and release procedures get short-cutted and this appears to be what happened here. The result is a product which can either go forward with lots of band-aids, bailing wire and spit holding it together (making maintenance a nightmare with limited reliability and success) OR a product that can be withdraw, reworked without the pressure of dealing with multiple daily reports of wide-ranging and serious bugs. I am attempting to be constructive based on my experience with software development in both types of environments - when development followed a sound set procedure through the process from design to release, and when shortcuts were taken to satisfy political, management, or marketing desires. I'm merely asking Sinew Software to withdraw a release that was clearly "not ready for prime time", and redo the effort properly with the technical process, issues and progress dictating release schedules rather than whatever pushed this one out the door before it was finished. Other major software development organizations have done this in the past, and users who see a company ready to admit a mistake then take proper action to fix it generally end up with higher regard and satisfaction with the developer than for those developers who "press on" with a bug-laden product, trying to pretend all is copacetic. In the end, the latter decision hurts the bottom line and ends up defeating whatever management / marketing decision drove the "pre-mature" release. I have downgraded to version 5, turned off auto-update for the extensions in the various browser that allow that, instead of having purchased the prime option on v 6 which was my intention though I did not need the features, but more as a reward for a an application and browser extensions I used and found perfectly met my need. But now, unless they take the proper action to fix ALL the issues in version 6 (withdraw, re-work, re-release being the proper way instead of endless little ad-hoc patches), I will be done with any / all products related to Sinew Software an use one of the password managers built into my internet security suites or available from another vendor at a reasonable price.
  8. I have the identical error when trying to roll back from Enpass 6.0.x installs to enpass_chrome-5.5.3 (unpacked in "Developer Mode"). I had uninstalled version 6.0.2, the extensions, and gone through the registry manually cleaning Enpass and Sinew software entries (and there are a TON of them). I noticed that the manifest.json file contains one very curious entry: "version": "6.0.0.1", I wonder if this line is trying to tell the extension to hook up with the application version 6.0.0 in order to force an update to Enpass 6 when the roll-back version installed is actually 5.6.10. Anyway, the developers' statement that it is not possible to rollback the Chrome extension version is true. And since Enpass 6 and its extensions are virtually non-functional (at least they do not function CORRECTLY) you'll either have to run the desktop app, copy / paste from it to form / login pages in Chrome, OR get another password manager that actually works and has developers that are a little more serious in testing software before major releases and who have made sure there is a working rollback pathway BEFORE dumping the major release into the public domain.
  9. wmc

    UI broken on HiDPI displays in v6 [SOLVED]

    Version 6.0.2 seemed to fix the initial scaling problem, but introduced others ("forgot" master password, can't find the "vault" with all my data, browser extension worked once, then in subsequent sessions keeps insisting I have not completed setup, including setting a master password...). BTW, if you try to manually execute the browser extension and get the error page telling you that Enpass is not installed (when it is) then try to open Enpass from the tray icon, (Windows 10) the scaling problem returns for the "set-up is not complete" panel.
  10. This release fixed the text display / display resolution issue. However, 6.0.2 STILL does not recognize any sites for which it has stored data. This occurs in any browser (Firefox, Chrome, Edge). When on a page where I expect Enpass to open a window, request a master password, then show the "info" for the page it already has stored in its vault, nothing happens. I have to manually invoke the extension, enter the master password, where I am presented with the "most often..." site then I have to type in a portion of the page URL to get the stored info for that page to appear in the Enpass pane. Or the " Enpass Assistant is unable to connect with the Enpass app" message appears. (The later seems random, but frequent and I can't tell what steps would recreate it as it happens on different sites, sometimes on first access, sometimes on a subsequent access.) The fact that this "dumbed down" behavior seems to be something no ones thinks is a problem makes me ask: Is this a new design / feature / functionality that Enpass intends to keep? If so, it may be time to find a new password manager with browser plug-ins / extensions that actually have a true auto-fill functionality like versions of Enpass up to 6.0.0 used to have.
  11. wmc

    How downgrade to Enpass 5

    Vinod, Thanks for your patience with a stupid user. After your reply I went looking for the link I obviously missed and found it near the bottom of the downloads page. Sorry for the bother, but thanks for the reply.
  12. Vinod, I had the same issue in 6.0.0 and 6.0.1. Enpass extensions in all browsers seem not to be aware of the active web page with login credentials which I open whereas in v 5.x.x extensions would pop open a window requiring me to enter my master password before it would release the browser window for further user interaction. If I then clicked on the Enpass icon in the browser menu / button bar, it would open an Enpass pan with the entry for the site on the active browser tab / page ready for auto-entry or for me to copy / paste individual fields. Version 6.0.x does not ask for a master password and seem oblivious to the fact that I opened a login page that has credentials stored in the Enpass "vault". I click the Enpass extension icon (browser menu / button bar) and it opens a pane (with the misaligned low-res text bug displayed) asking for a master password. When I enter it, the pane then shows the most frequently used entry instead of the entry for the site I on which I was active when I click the Enpass button. OR on some occasions when I click the Enpass extension button it goes through the routine saying it cannot communicate with the main application, and have I enabled browser extensions which has been done multiple times. It appears to me that communication between the extensions and their respective browsers became non-functional in v 6.0.x and communication between the desktop application and browser extensions became intermittent and unreliable. Perhaps more debugging and investigation of these messaging / data passing "channels" is needed.
  13. wmc

    How downgrade to Enpass 5

    We need to be able to roll back to the last version 5.x.x that was in place when version 6.0.0 update was pushed to us. Both the application and the extensions seemed to stop working as they had in 5.x.x. That is: When visiting a site that has login info, Enpass extensions (Firefox, Chrome and Edge) do not pop up a window asking for a "Master Password" in order to fill-in or allow the user to enter login credentials. "Manually" opening Enpass extensions do not present you with the stored info for the site / page you have open in your browser as it did in 5.x.x for sites with login info already entered in Enpass. You must run a search on the active page to have Enpass present the information, then you must copy-paste as auto-fill seems to be unaware it is on an auto-fillable page for which it has stored the information. The 6.0.1 update trashed the UI so that even those manual operations are, is some cased, not even possible. It appears that any scaling set in "Settings->Aystem->Display->Change the size of text, apps, and other items" gets applied to Enpass graphic elements (windows, panes, icons, menu 'real-estate', UI control gadget control real-estate) but not to its text elements. The text is also very small and low-res (VGA perhaps?) and with it mis-aligned, makes the user guess where the actual controls for the item described by the text (icon, menu item etc.) is located. And some of the control highlights overlay / underlay some of the tiny low-res text elements making them unreadable. (This bug described in multiple other topics so I won't add a screen grab here.) So, could you PLEASE post a location where we can download the last working version of Enpass 5.x.x and its compatible browser extensions that we can use until you get a working, fully tested version of Enpass 6.x.x available? Thank you.
  14. wmc

    UI broken on HiDPI displays in v6 [SOLVED]

    I have the same problem - graphics (like Icons, windows, panes, menu backgrounds) scale but the text does not so that the text labels do not line up with either the graphics or UI controls. The text also looks very ragged / low-res. Also, with 6.0.0, the browser extensions seemed to stop functioning: when I open a page with login info, Enpass does not pop a window up asking for my Master Password and I just operate the window as if Enpass doesn't exist. Occasionally I can open the Enpass UI from the browser button / menu bar, but sometimes it goes through the routine like it can't find the underlying application OR that I have not enabled the browser extensions which I have on multiple occasions, entering the multi-digit code as requests. For me the transition to 6.0.0 stopped Enpass browser extension from working, and now the 6.0.1 release has made it very difficult to control the desktop application and made some of the info impossible to read. I am also still confused by this "Windows Modern" vs. "Windows (Store)" vs. "Desktop Windows PC". Makes me wonder if I have the "wrong application and / or extension files installed. Finally, I would like to know if there is a store of previous versions so I could go back to the last version of 5.x.x that was working perfectly before the update. That is previous versions for a desktop, Windows 10 PC running Firefox, Chrome and Edge.
  15. Windows store version: Can't put a shortcut on the desktop; can't find the install directory so I can go there to create a shortcut to place on the desktop; can't get it to work with Firefox even after installing the EnpassNMHost_v5.5.1.0.exe. So, where do I get the "old style" desktop version I was using before Microsoft scrambled my system with an attempt to force an Office 2016 replacement of my Office 2007 suite? (I had to rebuild my system and when I went to download Enpass, it appeared the MS Store version was the only one I could download. ) Do I need to uninstall the MS Store version to get the desktop version to work? IMHO, the MS Store version was a VERY BAD idea. wmc
×