Open previously compiled executables

[Maineiac]

Is it possible to open and extract file contents of an existing .exe created in Setup Factory 7?

Thanks

[jassing]

Originally Posted by Maineiac

Is it possible to open and extract file contents of an existing .exe created in Setup Factory 7?

Thanks

No.
The archive file is encrypted and kept secret by IR.

if that were possible; that would negate any security aspect of SUF.

I know of at least two firms that tossed money into trying to do so.
One was partially successful in that they were able to extract names of included files, but not their valid contents.

[pww]

mmm, why not?
just run the installer and you're done - it will extract everything for you.
You may do that on a virtual machine and make system snapshots immediately before and after running the installer, then compare to see what files were installed or updated and what else has changed.
With some extra effort you can capture even temporarily created and then deleted files.

You can't unpack the installer, or bypass some installation pre-condition like entering a registration code, or capture files that don't get installed for some reason (like in case of a conditional installation).

[jassing]

Originally Posted by pww

mmm, why not?
just run the installer and you're done - it will extract everything for you.
You may do that on a virtual machine and make system snapshots immediately before and after running the installer, then compare to see what files were installed or updated and what else has changed.
With some extra effort you can capture even temporarily created and then deleted files.

You can't unpack the installer, or bypass some installation pre-condition like entering a registration code, or capture files that don't get installed for some reason (like in case of a conditional installation).

If I have s/n -- how can you "just install"?
if I have conditions (specific file or registry or com object must already exist) how can you "just install"?

So if you are allowed to install -- then do exactly as you suggest; but it would be a huge security hole if anyone could just "grab the install.exe and extract the files"
That bypasses the license screen, serial #s, etc to permit the user to use the files & indeed, perhaps some of the files shouldn't be installed.
I have one client with an installer with 3 different "FILE.DLL" in it -- if the user uses the wrong dll it WILL corrupt his system so allowing the user to extract the wrong file would opening a can of worms with regards to liability.

Your view clearly differs from mine -- but I, for one, think that no one should be allowed to simply "extract the files" from the install.exe

[pww]

Originally Posted by jassing

Your view clearly differs from mine -- but I, for one, think that no one should be allowed to simply "extract the files" from the install.exe

Actually my view (as long as I have a view on this subject) doesn't differ from yours much, if at all.
I noted in my post that you can't bypass installation pre-conditions or capture conditionally installed files. Just added that if none of these applies, it's easy to get what's in the installer.

As for security, for me the whole idea of securing the installer is wrong. The installer security ends with the first successful installation. The app itself should take care for this, not the installer.