Question about TCPBlock logging results
Hey
First thing: sorry if this is the wrong place for my question. Let me know if it doesn't belong here.
I just started using TCPBlock to log outgoing connections. Most of the output, in Console, looks like:
7/10/14 18:49:01.000 kernel[0]: tcpblock: allow connection of uTorrent to 89.212.176.159:37096 uid=501 pid=1795 proto=6
7/10/14 18:49:02.000 kernel[0]: tcpblock: allow connection of uTorrent to 88.123.8.213:61837 uid=501 pid=1795 proto=6
7/10/14 18:49:03.000 kernel[0]: tcpblock: allow connection of firefox to 127.0.0.1:12080 uid=501 pid=1989 proto=6
Note that, so far, I'm allowing all outgoing connections, I just want to get an overview of what the connections are.
Then there are the following events in between:
7/10/14 18:49:07.000 kernel[0]: tcpblock: allow connectcptionblock: of c aomllow connect.aion of cvast.promoxy t.avaso t.proxy t194.221o 1.65.23:80 u94.2id=0 pid2=889 proto=6
7/10/14 18:51:02.000 kernel[0]: tcpblock: tcallow connection of upblockTorr: allow connectenion oft fro uTorrent m 192.168.2.2:58240 uid=501 pid=1795to 70 p.189roto=6
7/10/14 18:53:27.000 kernel[0]: tcpblock: allow connection of com.tcavast.proxpblock:y altolow 23.co3.90.24nnection of com.a8:80 uid=0 pidvas=889 proto=6
7/10/14 18:53:32.000 kernel[0]: tcpblock: allow accept from 127.0.0.1:tcpblock: 584all50 toow c coonnection of com.m.avast.avast.proxypr to oxy uid=0 pi205.185d=889 proto=6
They appear to be tcpblock events as well, but look like they are permutations or garbled up versions of the above events.
Anyone knows what's behind this? Maybe related to avast, which at least in some of the events is mentioned as well (though not in all of them).