Vinod Kumar

Enpass team member
  • Content count

    99
  • Joined

  • Last visited

  • Days Won

    8

Vinod Kumar last won the day on November 22 2016

Vinod Kumar had the most liked content!

Community Reputation

28 Excellent

About Vinod Kumar

  • Rank
    Advanced Member
  • Birthday
  1. Hi @jasn, Thanks for trying Enpass on gentoo. You should install "lsof" as a dependency to fix browser connection error. Also, the proper way to autostart Enpass on system reboot is to enable "Autostart on system startup" option in Enpass settings. Other methods for auto-starting will lead to launch incorrect binary without properly initialing Enpass environment and hence "QSQLCIPHER driver not loaded" error. Cheers
  2. Hi @klktrk, You are right, It should be https://dl.sinew.in/mac/setup/Enpass-5.2.1.dmg. Our server is still supporting both protocols for legacy reasons. However, Enpass.app is properly code-signed and you can check verify signing certificate details with codesign -dv --verbos=4 /Applications/Enpass.app It should validate with following details: Authority=Developer ID Application: Sinew Software Systems (7ADB8CC6TF) Authority=Developer ID Certification Authority Authority=Apple Root CA Also, Mac Gatekeeper(with protective settings) will automatically block the launch of app it is not code signed properly. Cheers!
  3. Hi @Topa, You should set QT_BEARER_POLL_TIMEOUT variable with -1 value. QT_BEARER_POLL_TIMEOUT should come under variable column and -1 should be under Value column. A screenshot is attached for your reference.
  4. Hi @cimm, Enpass does have HDPI support. In most cases it works out of the box, but sometimes you might need to adjust a few environment variables to make it work. e.g. Please try adding following environment variables to force for 150% scale on your primary display. QT_AUTO_SCREEN_SCALE_FACTOR=1 QT_SCREEN_SCALE_FACTORS=1.5
  5. Hi @Airstar, Yes, you're right that TPM 2.0 is required for new hardware but api support for TPM 1.2 has its own limitations, and the one which is restricting the Full time Hello support on Enpass is lack of TPM key attestation info when asked for using the Microsoft provided APIs. TPM key attestation is a protocol that cryptographically proves that a key is TPM-bound. This type of attestation can be used to guarantee that a certain cryptographic operation occurred in the TPM of a particular computer. We use KeyCredentialManager.RequestCreateAsync() API to get authenticated encryption keys to protect the Master password. Now, we need to check where those keys are stored. It can be on a Hardware TPM or a simulated software TPM. To get this attestation information, we use GetAttestationAsync(), which is generated by the TPM chip. Unfortunately, Above api attestation information is only available TPM 2.0 or higher. So, in case of TPM 1.2 (one in your laptop) or a simulated software one, there will be no attestation information. We have no means to distinguish between a TPM 1.2 or software TPM. So limitation of API is the only reason that we support full-time Hello unlocking only on devices where keys guaranteed to be bound to hardware TPM. You can read about the related information in section 3.1 and 3.4 on https://docs.microsoft.com/en-us/windows/uwp/security/microsoft-passport#311-attestation Hope it helps!
  6. @Topa Can I see a screen shot of Envrionment variable, so that I can spot a typo just in case?
  7. Hi all, Thanks for bringing this topic. Enpass encrypted data file is a SQLCipher database. It is not possible to decrypt it without native SQLCipher support in browser. And as far as I know none of modern browsers provide a native implementation of SQLCipher.
  8. Hi @marc kranat, Enpass extension is trying to reach Enpass app through loopback interface. You need to add exception only for localhost ( 127.0.0.1) in your proxy configuration. Cheers,
  9. Hi @Ryan-linux, Thanks a ton for reporting the issues with Enpass DEB packaging. The extra files and typos are certainly the mistakes by packager and shouldn't be there. We will get them corrected in next version. For proper working, Enpass needs latest features and bugfixes in Qt which are always not available in older versions as different Debian based distros provides different versions of Qt. This will add up more time in testing without any significant improvement in quality. And this could flood our inbox with complaints of Qt incompatibility. The current solution, where we provide those Qt libs against which Enpass is compiled and hence a launch script, has been working fine without any incompatibility for many different version of various distros. I wish we had all the time and resources to keep the things align perfectly with DEB packaging guidelines. We appreciate all your love and support for us to keep improving Enpass with every update. Cheers!
  10. Hi @Topa, This work around should work universally on any version of windows. Also, you should logout and login again in order to change take effect.
  11. api

    Hi @s1lvester, Sorry, we don't have any ready to use apis to suit your purpose. This thing is in our roadmap from long time but with a very low priority. I hope someday we will have enough time and resources to implement it, but at the moment we are very busy with other important tasks. Cheers
  12. Hi all, This feature is still in beta. We are working hard to iron out all the bugs as soon as possible and make it public.
  13. Hi @MacFreek, Thanks for writing in. iPhone version currently supports only Basic authentication for WebDAV. We are aware of this limitation and will overcome it in future releases. Cheers
  14. Hi @Anthony, There are no updates for it as of now. Also, We are working on Edge extension that will work with UWP version of Enpass and will be available to download from Windows store.
  15. Thanks @Arthur Rump, noted. Need some time research it further. Will keep you posted.