How to convey the safety of a .vbs for download, in light of all the potential dangers of today?
Posted on 2007-03-19
What is a practical solution to prevent your perfectly safe .vbs script from triggering warnings.
[Or, at least, make it a little easier to 'swallow']
Thus far I have simply forewarned the user that this is the case. That they will see warnings etc.
But the other day, a new computer with Norton installed, made such a stink about it, it almost frightened me from running the script, and I'm the author!
I know you can purchase license with certain places [Verisign, I think is one] but the script is free and simple, yet useful - but I imagine many are afraid to use it.
I also realize, that if there were 'too easy' an answer to this, it would get abused, but thought I might ask anyway.
Maybe recommendations, and '5 star awards' type things ...