Login  | |
|
 |
RE: VBS to EXE - 6/26/2007 1:43:23 AM
|
|
 |
|
| |
ebgreen
Posts: 4613
Score: 31
Joined: 7/12/2005
Status: offline
|
If the script is running on an NTFS system and you control the command that is used to run it (i.e. a login script) then you can look at embedding the script in an alternate data stream as well. Then the user would need to know first that the script is in an alternate data stream and they would need to know how to find it.
_____________________________
"... when you are good and crazy, oooh, oooh, oooh, the sky is the limit!" - The Tick
Goog places to start:http://www.visualbasicscript.com/m_24727/tm.htm
http://www.visualbasicscript.com/m_47117/tm.htm
|
|
| |
|
|
|
|
RE: VBS to EXE - 6/27/2007 9:27:25 AM
|
|
|
|
| |
Fredledingue
Posts: 333
Score: 0
Joined: 5/9/2005
From:
Status: offline
|
One way to test such software more pragmaticaly:
Create a vbs script with nearly nothing in it, but a sleep of a 100 milliseconds.
Compile it into an exe.
Create a script with a loop which launch via shell, the exe file one thousand times and, with a timer, count the time it took to do so.
Repeat the operation with the vbs file and see which one is faster.
If the exe file launched faster, then it's probably a true executable. If it's an extractible, it should take longer.
_____________________________
Fred
|
|
| |
|
|
|
|
RE: VBS to EXE - 6/28/2007 11:32:04 AM
|
|
|
|
| |
dm_4ever
Posts: 2366
Score: 38
Joined: 6/29/2006
From: Orange County, California
Status: offline
|
I'm currently playing with a beta version of PrimalScript 2007 which will let you package HTA's, PowerShell, and VBScripts into .exe's. One main difference is that you will be able to compile your .vbs files and it will use it's own engine so that it runs in memory and of course it lets you specify alternate credentials and all the other stuff you can currently do.
_____________________________
dm_4ever
My philosophy: K.I.S.S - Keep It Simple Stupid
Read Me: http://www.visualbasicscript.com/m_24727/tm.htm
Frequently Asked Stuff: http://www.visualbasicscript.com/m_47117/tm.htm
|
|
| |
|
|
|
|
RE: VBS to EXE - 6/29/2007 1:02:23 AM
|
|
|
|
| |
ebgreen
Posts: 4613
Score: 31
Joined: 7/12/2005
Status: offline
|
This of course all brings us back to the question of the difference between a programming vs. scripting language. To be honest with you, in my opinion by the time that you get to the point that you are compiling your script and granting credentials, etc. you might as well have just written the thing in a regular progrmmaing language.
_____________________________
"... when you are good and crazy, oooh, oooh, oooh, the sky is the limit!" - The Tick
Goog places to start:http://www.visualbasicscript.com/m_24727/tm.htm
http://www.visualbasicscript.com/m_47117/tm.htm
|
|
| |
|
|
|
|
RE: VBS to EXE - 6/29/2007 9:33:53 AM
|
|
|
|
| |
Fredledingue
Posts: 333
Score: 0
Joined: 5/9/2005
From:
Status: offline
|
The problem is that I don't know any "regular" language and the little I'v seen didn't encourage me to learn them.
In my personal case, there is no use of "packaging" a scrpt in a self-exctractible.
Creating a fake executable, just for the sake of seeing another extention type in Explorer is not what we are looking for.
What we want here is a vbs to -at least- vb translator or to more modern languages.
A program which would create a source code out of a vbs file and that would let us modify this source code if we need to.
_____________________________
Fred
|
|
| |
|
|
|
|
RE: VBS to EXE - 7/4/2007 2:52:01 AM
|
|
|
|
| |
Parabellum
Posts: 222
Score: 0
Joined: 11/12/2006
From: UK
Status: offline
|
I spent a long time looking intro this subject.. and have posted many times relating to this subject before... to summerise... best option I found was Exescript 3. Firstly it encrypts the file contents... and it also executes the packaged EXE in memory, instead of writing to a temp folder, so making it pretty near impossible to read the contents.....
It would in fact probably be easier to decompile an executable!
|
|
| |
|
|
|
|
RE: VBS to EXE - 3/8/2008 12:15:32 PM
|
|
|
|
| |
TNO
Posts: 1061
Score: 10
Joined: 12/18/2004
From: thenewobjective.com
Status: offline
|
I must admit I'm a bit paranoid of this program, though maybe unjustifiably so. I played with some basic things and I must say first off, I hope no one minds the size of this...
MsgBox "Hello World!" --> 188kb exe.
If you plan to deploy a script using this keep that in mind. Also under windows Vista there is a good chance you will still receive warning dialogs (I do, and UAC is disabled)
If you have a small script of only a few hundred lines I would suggest not using this. By the time the .exe loads you could have run the vbs a few times already.
I purposely invoked an error and the error dialog displayed the title XNeat on it. I don't know anything about this application, but it appears to be some type of generic utility. Anyone with more info on this would be welcomed.
Also, you're resulting .exe will require the .NET framework to be installed as well it seems so that's something to note if you handle older windows systems. (I ran the program through a Hex editor since the website isn't very clear behind the .exe's creation).
You're vbscript is not necessarily going to be compatible with this "compiler"/wrapper. For example: WScript.Echo will fail. Your usual global objects are not available so be sure to look over your script beforehand.
All things considering, if your paranoid about an individual script and want it protected from prying eyes, go for it. Personally I dont see this as an elegant solution, and can often be more trouble than its worth. Good effort though by the author I guess.
Edit: I don't know why its being referred to as a True .exe It looks to be as much of a wrapper as the other programs being offered.
< Message edited by TNO -- 3/8/2008 12:16:54 PM >
_____________________________
Consolidated Script Component: The Acid Test
A universe of complexity...
|
|
| |
|
|
|
|
RE: VBS to EXE - 3/9/2008 6:03:32 AM
|
|
|
|
| |
TNO
Posts: 1061
Score: 10
Joined: 12/18/2004
From: thenewobjective.com
Status: offline
|
At any rate, from 21 bytes to 43kb is still pretty significant. But I assume that's without just the initial overhead of the run time, and the size will go down from there to a more linear growth.
Sa6ry, I found your website and have wandered through it for a few minutes, since your website is brand new I couldn't find alot of the information I wanted to. Hopefully when you finish your documentation page it will clarify some things. Especially the current limits of this beyond core vbscript functionality.
_____________________________
Consolidated Script Component: The Acid Test
A universe of complexity...
|
|
| |
|
|
|
|
|
Printable Version
RE: VBS to EXE - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread