Basically, I'm trying to get a password out of a setup file so I can run it...

I've searched through hundreds (probally literally) of pages reading about cracking but I've yet to do anything that works with setup files.

Password : Blank

Should I just give up now, or is there a way?

With some installers the password is only implemented in the setup script and not the archive itself, so with knowledge of the compression format one can easily unpack the installer.

Others, however, may be of a higher security and use a hash , etc.

Start debugging it.

To add to what LLXX said, some installers don't even use the actual password - just a CRC32 or other checksum value (InnoSetup is known to do it), so "fishing" for a password is impossible.

Fortunately, InnoSetup is open source and someone has made a complete unpacker/decompiler to extract everything. Odd though, it doesn't ever ask for a password before unpacking.

There are plenty of other programs that can take apart install packages (like MSI's) and allow you to "tweak" the install script.


Your first job should be to determine the install package used. Once you know that, what you can do to the installer is easier to figure out.

I think it is not against the rules to post here the installer brand Wise? InstallShield?
Then more specific suggestions could be made.

If it unpacks the files - (it will usually tell you), before it asks for the password, here is an easy, (and safer than an HBOOT), method to get to the install files and possibly the install script - run the installer using olly, when it asks for the password simply quit olly - then go to your documents and settings directory, and search for files made within the last few minutes - in those files you may find a script describing the install events - the object here is to eliminate the password requirement - any "password" you find in the script is probably just a seed and not the actual password, with the Wise installer it's possible to debug the installer itself and patch around the password - however sometimes everything seems fine - but I've had occurances of spontaneous reinstallation occuring when other progs are run.

SiGiNT

I'm not sure if this one is actually a brand.

See, it's not a company that made it...it was just a person.

Anyway I could find out real quick if it does?

and it just asks for the password right after I accept the agreement.

Keep in mind our prohibition of identifing BOTH target AND posting code. You can discuss CODE without identifying the target and removing identifying information FROM code, if you post some.

If some people want to know "exactly" what your target is, or want to take a look at it themselves, you can discuss those things by PM. Make sure you review the FAQ discussion of these Rules!



Regards,

Two Methods:

1. Run a setup decompiler (yes, search on google, there is one for wise, there is one for installshield and yet so many more) and get all files as normal.

2. Run your installer in a debugger and break on any *gettexta commands and you can change the path from there. Hint: Even something as rudimentary as IDA Debugger works, so I am sure Olly/SICE will work. I use Microsoft Windbg though...

Have Phun