Idea about Norton

[Bob Sneidar]

I think this is the wrong way to go about it. I don't think Norton simply counts the number of times software attempts to install without signing, and then has a threshold where it accepts the unsigned installation without challenge. I have noticed however that sometimes installation instructions include the disclaimer, "You may need to suspend or disable you Antivirus software to install this application." Or something along those lines. Perhaps you need to distribute an Installation Notes text file with your application?

I actually have encountered print driver software that WOULD NOT WORK as long as a certain OEM distributed AV software was running on the workstation.

Bob S


On Jan 23, 2017, at 10:12 , tbodine via use-livecode <use-livecode at lists.runrev.com<mailto:use-livecode at lists.runrev.com>> wrote:

Hi Graham.

I wanted to float a rough idea off-list... Tell me what you think.

If Norton faults our files for being new and not (yet) popular,  perhaps we could generate a base of download activity ourselves to get over the threshold. Specifically, I'm thinking of an informal group of software authors who form a "mutual download society."

Say we had 10 authors to start who agreed to download one another's product file(s) once a day for a month.  At worst, we'd probably learn some things about what Norton counts, what it ignores, and what is the threshold to move to a trusted level. At best, we might help each other to win acceptance.

For those of us with fast, unmetered connections, there's virtually no cost to the downloading of files other than the time it takes to do it. And with Livecode we could easily write a stack to automate that job.

Thoughts?

Tom Bodine