Jump to content

goldpeter81

Members
  • Content Count

    4
  • Joined

  • Last visited

  • Days Won

    1

goldpeter81 last won the day on May 10 2016

goldpeter81 had the most liked content!

Community Reputation

2 Neutral

About goldpeter81

  • Rank
    Newbie
  1. This isn't as easy as you might think. If you implement TOTP you need "somebody" like a server (the Enpass client) who verifies whether the code is correct. So when somebody stole your Enpass database the Enpass client on you PC can't verify the code and the protection is broken.
  2. For me it seems to be the same. Joining there.
  3. I come from another post and have nearly the same setup as the others here in this post. I tested on a Windows 10 and 7 Machine both with ESET Smart Security and it doesn't work in Chrome and any other Browser. I'll do some VM testing and report back with some details. EDIT: VM testing Tested Enpass 5.2.0 on fresh Windows 10 without ESET Smart Security installed and it works in Chrome and Firefox. With ESET installed nothing works at all. After removing ESET everything worked again.
  4. Hello, I installed the Enpass extension in Chrome and activated it in Enpass, but I keep getting an Connection error. I tried to install the extension in other browsers and disabling the signature verification but nothing changed. Reinstalling Enpass and/or Chrome didn't helped at all. I analyzed it with TCPView and there is indeed an open connection on port 10391. In Chrome's Dev Tools it seems that the extension cannot access Enpass because of the error: WebSocket connection to 'ws://localhost:10391/' failed: Invalid frame header I installed Enpass with Chrome on a VM and it worked like a charm, so I would be very happy to see this error solved for me. Greetings
×
×
  • Create New...