I've been using the current versions of DirectParse for some time now, prior to that I've used several different versions as well as DVS Parse. Today I noticed some unusual behavior after I updated the memlock and opened up DirectParse to parse a dynamis run.
My personal firewall detected DirectParse attempting to make a connection to 8.14.216.16 over TCP/80. I've never noticed this before, and as I said, I've used this same version for quite a while (haven't reinstalled it or anything). Since I was in dynamis, I just blocked the traffic and was unable to perform a packet capture. Can anyone explain this?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've been using the current versions of DirectParse for some time now, prior to that I've used several different versions as well as DVS Parse. Today I noticed some unusual behavior after I updated the memlock and opened up DirectParse to parse a dynamis run.
My personal firewall detected DirectParse attempting to make a connection to 8.14.216.16 over TCP/80. I've never noticed this before, and as I said, I've used this same version for quite a while (haven't reinstalled it or anything). Since I was in dynamis, I just blocked the traffic and was unable to perform a packet capture. Can anyone explain this?