Jump to content
Enpass Discussion Forum

tox1c90

Members
  • Content Count

    22
  • Joined

  • Last visited

  • Days Won

    2

tox1c90 last won the day on September 2 2020

tox1c90 had the most liked content!

Community Reputation

13 Good

About tox1c90

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. As I already pointed out in the Beta forum, the issue might be related to the Infineon TPM. https://discussion.enpass.io/index.php?/topic/21265-say-hello-to-full-time-windows-hello-with-enpass-beta-ver-650/&do=findComment&comment=38797 I was not able to get it to work with Infineon. Only after I swapped it for a Nuvoton TPM, it started to work immediately. In my case, Windows was throwing a certificate error for the Infineon TPM on each reboot. Look at your Windows event log if you see something like that once per reboot. That error was not related to Enpass at all, bu
  2. I wasn't able to get it to work using the Infineon TPM 2.0 module on my Asrock board, despite using the latest firmware. Also tried clearing the TPM and setting everything up from scratch (Windows Hello, Bitlocker TPM and so on...). I also noticed that the event log throws a Certificate Error on each boot regarding the TPM attestation, saying that the public and private key are not cryptographically bound. Most likely this is also the problem that leads to the failed check which Enpass is calling. However, I was able to fix the problem - by removing the Infineon TPM module and puttin
  3. I am talking about the store version, of course. I got it working now on another computer, which is a Surface Go tablet from Microsoft. Only difference in configuration which I am aware of is that it's using a different TPM. The Surface Go is using it's Intel fTPM (firmware/platform TPM 2.0), while my desktop computer has a discrete Infineon TPM module (also TPM 2.0, latest firmware). Both claim to fully support "Key attestation". I remember last time I was using the old Enpass UWP version (which already had full-time Windows Hello), I was using a different discrete TPM module o
  4. Hi @Kashish, I just updated to 6.5.0 and had to re-enable Windows Hello (maybe it got disabled due to the changes made for full-time Windows Hello support). However, it seems like it is not working as intended for me, because it says "Master password is required every time you restart Enpass". So I restarted Enpass and indeed I had to enter the master password. Are there any additional requirements for the full time Windows Hello support? I know that it worked on my PC using the old Enpass UWP for Windows 10. There I had the full Windows Hello support because I fulfilled all the requ
  5. Hi @Anshu kumar, did you get any feedback on this issue? I ask because it's still happening on latest Enpass (Windows Store). But it's happening under slightly different conditions compared to the original issue. Right now, it is only happening when Enpass vault becomes locked and minimized to system tray, but unfortunately every time. New steps to reproduce quite easily: 1. Launch Enpass and unlock vault in main window 2. Lock vault by pressing the "lock" icon in main window 3. Press "X" to close main window so that Enpass is minimized to system tray icon 4. Open
  6. Hi @Anshu kumar, for some reason the problem appears to be back. I'm pretty sure everything was fine until 6.12 (including), so I think it came back with 6.20 or one of the latest updates. Could you please check on your side?
  7. Hi! I recently started using Android 9 and 10 (got the update a few days ago on my Google Pixel 3a) and tried out the new Autofill API in my browser (Microsoft Edge for Android). Unfortunately, this turned out to be a really bad experience. While autofill via accessibility service was working really great on almost every website (independent from language), it goes horribly wrong when doing it via the Android autofill API. I noticed that on all German sites Enpass will just fill the mail address / user name into both login fields (mail/username + password). So it does not fill the pa
  8. Hi @Anshu kumar, after running and testing the latest Enpass update 6.1.1 for several days now, I can confirm that it is not longer raising platform timer resolution! Thank you for fixing it
  9. Unfortunately I have to report that this is still an issue. But I narrowed it down to a single case: The power bug appears, when vault is locked and main window closed so it runs completely in the background and does only appear as systray icon. So exact steps to reproduce: 1. Launch Enpass, but do not unlock vault. 2. Close Enpass main window using "x" on top right corner of the window. Thus Enpass is still running in background but only shows as system tray icon. 3. Open elevated Powershell, run: "powercfg /energy /duration 10" 4. Open energy-report.html, scroll
  10. Looks like it is only happening when Enpass is launched automatically and minimized together with Windows. I was not able to reproduce it after closing Enpass and starting it manually.
  11. It is really strange that you guys are facing so many problems... I'm using Enpass 6 on both Windows 10 (with Edge browser extension) and Android since it was made available as Beta in Windows Store, and I haven't experienced any severe or functionality breaking issue so far. The communication with Edge extension even works much better with v6 compared to v5. Not for one second I thought about downgrading to the previous version. Looks more like compatibility issues which needs to be fixed for you, and not as if Enpass 6 itself is broken.
  12. @Hemant Kumar I have to re-open that case. With the update it seems to be partially fixed. In the state when Enpass application is fully opened (see upper screenshot "Enpass main window.jpg") the problem is fixed and Platform Timer Resolution is at default now, so Windows energy report does not show a warning anymore. In the state when Enpass is running in extension mode (see lower screenshot "Enpass taskbar.jpg"), that means when left-clicking the Enpass icon just pop-outs a small Enpass window docked to the taskbar, the Platform Timer Resolution is still increased to 1ms by Enpass
  13. Hello! If Enpass 6 is running minimized in the background / tray icon and the vault is locked, the Windows Platform Timer resolution is increased from the default 15.6ms to 1ms by Enpass process, which causes significantly lower CPU C state usage and thus less battery life. Steps to reproduce: 1. Let Enpass 6 start automatically with Windows, or start it and minimized it to the system tray, but do not unlock the vault yet 2. Run "powercfg /energy" within Windows PowerShell and let Microsoft power diagnostics generate an energy report 3. The report will show a warning,
  14. Hi! I was using Enpass UWP for Windows 10 with full-time Windows Hello enabled, because my computer fulfills all necessary requirements (TPM 2.0, UEFI Secure Boot). So Enpass UWP successfully detected that the machine is secure enough to store the keys in hardware/TPM and use Windows Hello directly on the first launch even after a computer restart or when Enpass UWP was completely closed. Now with Enpass 6, it is only using the fallback solution of asking for the master password the first time after restart, and using Windows Hello only for subsequent unlocks. I think Enpass 6 is gre
  15. What is about full-time Windows Hello, when the computer fulfills all the requirements needed for it to work in the Enpass UWP app? I have UEFI boot with Secure Boot, TPM 2.0 module, Windows Hello working with TPM, and was already successfully using full-time Windows Hello with Enpass UWP. Will it also be supported by Enpass 6? Or is it already for people that fulfill said requirements?
×
×
  • Create New...