Encode/Encrypt/Protect VBScripts

We have written some VB scripts that help us manage SQL Logins and
Users.

There is sensitive password data in the scripts and I was wondering
what the best practice is for encrypting or protecting the scripts from
prying eyes.

I saw some posts about the Microsoft Script Encoder, are there any
other options?

Any ideas are greatly appreciated.

Justin
Fri Dec 08 12:42:56 CST 2006

On Fri, 08 Dec 2006 11:31:25 -0600, <ABSnook@gmail.com> wrote:

> There is sensitive password data in the scripts and I was wondering
> what the best practice is for encrypting or protecting the scripts from
> prying eyes.

There is no non-reversable way to encode a VBScript file, so the best
practice is actually to not put such sensitive information in the script
at all. Can you use a trusted connection instead of a username and
password? The only other secure option I can think of would be to use the
CryptoAPI to encrypt the password in the script, but that would only mean
you would need a password to get the password, which I imagine defeats the
purpose.

--
Justin Piper
Bizco Technologies
http://www.bizco.com/

Les
Fri Dec 08 13:36:40 CST 2006

If you've got the 100$, ASE (http://www.adminscripteditor.com/) is able to
convert .vbs to secure executables.

Les

<ABSnook@gmail.com> wrote in message
news:1165599085.159709.261390@j72g2000cwa.googlegroups.com...
> We have written some VB scripts that help us manage SQL Logins and
> Users.
>
> There is sensitive password data in the scripts and I was wondering
> what the best practice is for encrypting or protecting the scripts from
> prying eyes.
>
> I saw some posts about the Microsoft Script Encoder, are there any
> other options?
>
> Any ideas are greatly appreciated.
>

JHP
Fri Dec 08 14:08:58 CST 2006

Another one we use, and fairly cheap, is VBS2EXE

<ABSnook@gmail.com> wrote in message
news:1165599085.159709.261390@j72g2000cwa.googlegroups.com...
> We have written some VB scripts that help us manage SQL Logins and
> Users.
>
> There is sensitive password data in the scripts and I was wondering
> what the best practice is for encrypting or protecting the scripts from
> prying eyes.
>
> I saw some posts about the Microsoft Script Encoder, are there any
> other options?
>
> Any ideas are greatly appreciated.
>