KeePassRPC seems to listen on any interface on linux

[finkelamein]

root@enterprise:~# netstat -tulpen | grep 22374 tcp 0 0 127.0.0.1:36392 0.0.0.0:* LISTEN 1000 1753595 22374/cli
tcp 0 0 127.0.0.1:12536 0.0.0.0:* LISTEN 1000 1752820 22374/cli
tcp 0 0 0.0.0.0:12546 0.0.0.0:* LISTEN 1000 1752819 22374/cli
root@enterprise:~# ps aux | grep 22374 lameinf 22374 1.4 1.5 880592 61624 ? Sl 15:11 0:06 /usr/bin/cli /usr/lib/keepass2/KeePass.exe

Could it be that this also causes the issues connecting to my keepass i'm experiencing?

i'm running the latest beta from mozilla sandbox with mono 3.2.3+dfsg-5

[luckyrat]

What is port 36392 for? Do you have other plugins installed apart from KeePassRPC?

The presence of port 12546 suggests you're running KeeFox 1.3 (I think that's what you mean by "mozilla sandbox").

So it looks like the web socket listener in KeeFox 1.3 is listening on all interfaces, whereas the older connection mechanism (still present in KeeFox 1.3 for backwards compatibility) is tied to only localhost.

I don't see this behaviour on Windows so it does look like a Mono-specific issue. Or maybe it's specific to your system... I wonder if your system has "localhost" defined correctly to point to 127.0.0.1?

Have you mentioned the "issues connecting to KeePass" elsewhere?

I don't see why this should cause connectivity problems but perhaps it's a symptom of another problem that might do.

[finkelamein]

I hate it when this happens:

Now my keefox connected and reauthenticated to keepass.

Differences in situation:

• wireless vs. wired (wireless at home, wired at work) debunked that, using wired at home, still working
• firewall starts eratic, but was able to verify it even works with firewall enabled

Just before this report i completely removed both keepass and keefox, to no avail.... (including about:config settings and all caches i could find) it just wouldn't connect and/or reauthenticate

But there has been a reboot since reporting this issue... i read something about sockets being held by firefox? Maybe it was that....

I'll close the issue....