search

pfn / keepasshttp

KeePass plugin to expose password entries securely (256bit AES/CBC) over HTTP
GNU General Public License v3.0
1.99k stars 275 forks source link

keepasshttp stopped to work on Win8.1 prof #195

Open lduczmal opened 9 years ago

lduczmal commented 9 years ago

Hi, A few days ago I installed keepass 2.25 with keepasshttp 1.8.4.0 on my win 8.1 prof machine. I configured Waterfox and chrome browsers and it worked fine. Today I added new DB to my keepass and keepasshttp stopped to work. Reboot and changing from plgx to dll version of plugin and closing newly added keepass database didn't help. TCPView (tool from sysinternals) shows that TCP port is opened by process System and has state "listening" but browsers reports that keepasshttp is not running. What could be wrong, How can I diagnose/debug it? Best regards Łukasz

peter-volkov commented 9 years ago

What keepasshttp client do you use? I have the same problem with chromeIpass 2.6.8" for last 12-14 hours.

I localized the problem - I use Yandex browser instead of chrome. In chrome works fine for me. And Yandex just can't send POST to localhost:19455

lduczmal commented 9 years ago

Hi, I have installed both waterfox (it is 64-bit firefox) and chrome and both stopped connecting to keepass. So I decided tu use another plugin - keefox (by Chris Tomlinson) but it also doesn't work. I suppose that something in my OS blocks communication with port created by keepasshttp and keepassRPC (keepass part of keefox), but I haven't any idea how to debug it. There are no entries in windows log, also keepass plugins does not create any debugging information.

ghost commented 9 years ago

For me it stopped working on Firefox and Chrome running on Windows 8.1 after the most recent update of KeePass (2.28) on both my personal notebook and also on my work notebook. On both system Linux is installed too and there it still works like a charm, KeePassHTTP 1.8.3 as well as 1.8.4 with KeePass from versions 2.25, 2.27 and 2.28.

I tried wireshark with Chromepass set to connect to LAN-IP instead of localhost but still nothing on port 19455, seems Windows is smart enough to not use physical interfaces for internal connections.

When I found a way to sniff localhost on Windows with free software I can probably tell more :)

Or could somebody tell me what I could request using netcat? A simple "GET /" doesn't seem to be useful as I get only error 400 on both Windows and Linux.

ghost commented 9 years ago

...seems alright again since Windows Updates have been installed last week.