Antivirus / Spyware / Adware strategies
Hello,
I would be interested to hear from fellow packagers what strategies (if any) they adopt to avoid developing and distributing packages that could potentially contain viruses, spyware or adware.
I was thinking specifically of when either legacy or in-house developed applications are repackaged using a snapshot methodology. In my experience it is quite commonplace for captures to be performed on clean builds with (for example) antivirus software either disabled or even absent.
Also, do most packagers routinely peform a virus / spyware / adware scan on such software both prior to any repackaging activity and also post-repackaging.
Regards,
Spartacus
I would be interested to hear from fellow packagers what strategies (if any) they adopt to avoid developing and distributing packages that could potentially contain viruses, spyware or adware.
I was thinking specifically of when either legacy or in-house developed applications are repackaged using a snapshot methodology. In my experience it is quite commonplace for captures to be performed on clean builds with (for example) antivirus software either disabled or even absent.
Also, do most packagers routinely peform a virus / spyware / adware scan on such software both prior to any repackaging activity and also post-repackaging.
Regards,
Spartacus
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
Inabus
16 years ago
I package on a vmware machine that doesnt have network access and of course no anti anything. Everything I need on the vmware is dragged from a cd to the vm or from my pc to my vm.
P
P
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
