Re: Can I compile / package up client side vbscript so an end user can't view it in a html file? by Martin
Martin
Wed Nov 30 10:39:19 CST 2005
Any idea what the encoder is called?
Completely agree with you regarding not relying on client side scripts but
I've had a project dumped on me that is already live and wanted a quick &
low-risk way of making it slightly more secure.
The client app doesn't communicate over the web, so I'm mainly trying to
keep out the people who like to fiddle with stuff - they usually break it...
Ta
Martin
"jg" <junk@mail.pls> wrote in message
news:uB8Wysc9FHA.2676@TK2MSFTNGP15.phx.gbl...
> try to make it difficult to view by using the free encoder from
> Microsoft..
>
> making script "can't view" is not possible. for all users. In any case you
> should not rely solely on the client side script for security nor validity
> of input. Your server side code should still make sure the input is valid
> and from the right source. Good old day of safety in the net is not
> around any more.
> "Martin Pritchard" <martinpritchard@newsgroups.nospam> wrote in message
> news:%23rRegJc9FHA.1028@TK2MSFTNGP11.phx.gbl...
>> Hi,
>>
>> Sorry if this is a stupid question, but I'm a bit new to vbscript...
>>
>> We've got a client app written so it uses client side vb script in a few
>> html pages to provide basic functionality (don't ask why, someone else
>> designed it!). The problem is, you can do the classic 'right click, view
>> source' and find out exactly how it all works. Not too great eh?
>>
>> My first question is: Is there a way to remove the vbscript and compile /
>> obfuscate it into a package which can be included into the project?
>>
>> Now, we've also got a web site which is also vbscript heavy which has the
>> same problem. And so, same question again for this...
>>
>> Thanks in advance,
>>
>> Martin Pritchard
>>
>
>