Jump to content
Enpass Discussion Forum

Ben

Members
  • Posts

    2
  • Joined

  • Last visited

Posts posted by Ben

  1. Hi all,

    Sorry for the late reply. I was able to solve my problem.

    The issue was caused by HSTS. I sometimes use ssh tunnels to connect to management interfaces of devices behind a bastion host. One of theses devices is using HSTS and from that point every connexion to localhost required an HTTPS certificate.

    Safari extensions connecting to localhost honour HSTS policies, so the connection to Enpass from the browser extension was not possible anymore.

    To solve it, I had to completely close Safari (and kill all process related to Safari in the Activity Monitor) and delete the following file: ~/Library/Cookies/HSTS.plist.

    Cheers,

    Benjamin

  2. Hi all,

    For about a week now, the Safari browser extension stopped working, displaying only a ‘Enpass Connection Error’.

    It works fine with the Chrome extension and the taskbar helper.

    When doing a tcpdump (sudo tcpdump -i lo0 portrange 10391-10395 -nnn) on the loopback interface I can see traffic from the taskbar helper or the Chrome extension to Enpass. However, I don't even see a connection attempt from the Safari extension.

    Here are the relevant open sockets (I am using Dropbox sync, hence the first connection):

    % sudo lsof -i -n -P|grep Enpass
    Enpass     949        bcollet   29u  IPv6 0x227f399a5755c0cf      0t0  TCP [MY IPV6 GOES THERE]:49721->[2620:100:6022:7::a27d:4207]:443 (ESTABLISHED)
    Enpass     949        bcollet   34u  IPv4 0x227f399a5dc33e77      0t0  TCP 127.0.0.1:10391 (LISTEN)
    Enpass     949        bcollet   40u  IPv4 0x227f399a5dc32bb7      0t0  TCP 127.0.0.1:10391->127.0.0.1:49484 (ESTABLISHED)
    EnpassHel  954        bcollet   11u  IPv4 0x227f399a68114bb7      0t0  TCP 127.0.0.1:49484->127.0.0.1:10391 (ESTABLISHED)

    I tried to reinstall the browser extension and Enpass. I restarted (and updated) my Mac. I still have the issue.

    In the extension's source code I saw that it's using ‘localhost’ to contact Enpass, and as Enpass is only listening in IPv4 I tried to comment the IPv6 localhost entry in my ‘/etc/hosts’ file, to no avail (it should fall back to IPv4 anyway, but I am starting to consider sacrificing chickens and drawing pentacles on the floor).

    Here are the versions I am using:

    •   Safari Version 11.0.3 (13604.5.6), then updated to 11.1 (13605.1.33.1.2)
    •   Browser Extension 5.5.2
    •   Enpass 5.6.3 (138)
    •   macOS High Sierra 10.13.3 (17D102), then updated to 10.13.4 (17E199)

    Any help is appreciated,

    Cheers!

×
×
  • Create New...