Postby generalzod » 20 Aug 2010 05:00
I don't think so, Outpost is reporting that
vlc.exe is attempting to listen to a port - localhost:loopback, TCP:49291
where the port itself varies slightly but is always in the low 49000 range.
If I allow that, then I see an attempt at an outbound connection to the same
port on the loopback connection.
Only after both of those succeed, it attempts to connect to ganesh.vlc.XXX
to perform the update.
So for some reason it connects to itself through a local TCP port before
going onto the internet. Seems harmless, but why?