Leaderboard

It has been one month since the release of 6.8.3 and we still continue to receive the same BS response and ask to be patient. Patience has run out! So I'll ask a different question to spare myself the anguish of your canned response: What are you going to do for your subscribers for this intolerable inconvenience???

I had some problem, and your support say workking in process. What is the release roadmap? The app cannot be accessed is very frustrating.

That is the problem. Credentials does not get persisted in the TPM, you are requested to type in the master key when Enpass start. Once it is started MS Hello works as expected. In the option it is written "Master password is required every time you restart Enpass"; it should not act like that if you have a properly configured TPM. It used to work for a while, but it broke and nobody really care anymore apparently.

Dear support, Since a couple of weeks we have a problem with enpass with a combination of Google Drive When enpass tries to synce enpass crashes with the following in the log Info: [HTTP] Using AUTO Proxy detection Info: [HTTP] Enabling VERIFY SSL PEER/HOST Info: [HTTP] CURLSSLOPT_NO_REVOKE Info: [HTTP] Using AUTO Proxy detection Info: [HTTP] Enabling VERIFY SSL PEER/HOST Info: [HTTP] CURLSSLOPT_NO_REVOKE Info: [HTTP] Using AUTO Proxy detection Info: [HTTP] Enabling VERIFY SSL PEER/HOST Info: [HTTP] CURLSSLOPT_NO_REVOKE Info: [HTTP] Using AUTO Proxy detection Info: [HTTP] Enabling VERIFY SSL PEER/HOST Info: [HTTP] CURLSSLOPT_NO_REVOKE Info: [HTTP] Using AUTO Proxy detection Info: [HTTP] Enabling VERIFY SSL PEER/HOST Info: [HTTP] CURLSSLOPT_NO_REVOKE Info: [HTTP] Using AUTO Proxy detection Info: [HTTP] Enabling VERIFY SSL PEER/HOST Info: [HTTP] CURLSSLOPT_NO_REVOKE I have also send a crash report with a link to this post. We use Windows 10/11 machines with Different versions of enpass. Version 6.8.3 beta ( web version) Version 6.8.3. ( 1153) Windows store version. I also send a crash report with a link to this forun post. If you need more info let me know.

Thank you very much for your answer. While I realize that you are doing your best to keep us posted, I am longing for more. In a few weeks we will celebrate the 2-year anniversary of this topic. We are past the monitoring of feedback (it has been clearly established that it is broken); now either Enpass is unwilling to fix this, or it depends on broken external dependencies (i.e. broken TPM API, ...). Either way it would be fair to let your customers know.