Comment 7 for bug 568154

It's not running a scan -- that was a firewall access. I know for sure it wasn't running a scan or trying to prevent file access because it had already done its weekly scan the day before, and the file access was by my account running a local command on a file in my own directory. The particular version of virus checker I have does not check file accesses at all, let alone to user files -- if a virus checker does watch file accesses, it's usually only system files they watch.

Do you know what might be trying to connect to TCP port 1346? Is there a license manager in use?