How to convey the safety of a .vbs for download, in light of all the potential dangers of today?

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 ...

-David
oprausAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

sirbountyCommented:
The best defense is a good offense? :)
Not really much you can do to make scripts appear less threatening.  Thanx to all the 'nasty' scripts out there.
I would just say have you scripts availabe for download with a disabled extension like script.txt and request the user rename it to vbs when they're ready to run it.
Also make sure you comment it heavily - what the script's purpose is in the header, and details on different functions within your code.  That way there's no question and the user is at least a bit more comfortable, whether they understand scripting or not, that you've at least taken the time to explain yourself.  Doesn't guarantee that they'll run it, but it puts you in a better position of being responsible enough to add disclaimers...
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
fostejoCommented:
opraus,

Unfortunately, with scripts automatically falling into the category of 'untrusted' by AV software etc, avoiding the warning messages is practically impossible unless you're willing to rename them to a 'docile' format such as .txt as sirbounty suggests.

To soften the blow for the user, you could perhaps hilight the advantage of distributing a VBscript over other types of download such as a normal executable - at least with a script, you can actually see what's going to run, how it works and, if so inclined, re-use some of the code .. you simply don't get these options with a .exe file etc.

cheers
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Scripting Languages

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.