answered
2014-12-10 19:33:34 +0000
This post is a wiki.
Anyone with karma >100 is welcome to improve it.
i3status does not open a listening socket:
sudo netstat -np | grep i3status | wc -l
0
However, it indeed creates a UDP socket:
$ sudo lsof -n -p $(pidof i3status) | grep sock
i3status 26396 michael 3u sock 0,7 0t0 268864 protocol: UDP
The places in the code where sockets are created are
http://code.stapelberg.de/git/i3statu...ipv6addr.c?id=3818dabcebea7f98e3dfdfbe5be42374bb60cf88#n24
and
http://code.stapelberg.de/git/i3statu... (which is used in http://code.stapelberg.de/git/i3statu...ethinfo.c?id=3818dabcebea7f98e3dfdfbe5be42374bb60cf88#n35)
But as I said, those are not listening sockets, so it shouldn’t pose a security problem.
I does not do so on my machine, at least `sockstat` does not show anything. Could you please add the relevant output of `sockstat`? Also, a bit of information about your system could help: which distribution, version of *i3* and where from did you get it?
% sockstat -4 USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS user thunderbir 983 35 tcp4 192.168.0.34:21445 xxx.xxx.xx.xx:993 user thunderbir 983 40 tcp4 192.168.0.34:21453 xxx.xxx.xx.xx:993 user firefox 979 65 tcp4 192.168.0.34:
try sockstat -4 -l