Using AutoIT to call an msi? Major concern

[turbochugz]

I have been wanting to use AutoIT to compile a script which entails running an msi file with administrator rights.

My concern is not so much the script, but the source file.

for example: i create a script that launces 123.msi with administrative credentials to install the 123 program. My question if one was to replace with the 123.msi with a differenent software product and call that 123.msi. Will my script continue to run and install the newly renamed 123.msi file? I dont see any methods or validation checks to prevent this from happening as it is simply a script.

I hope i was clear.

Thanks.

[bogQ]

use FileInstall() so that noone can rename until run.

use FileGet*Size() or something similar to identify file.

Edited August 21, 2012 by bogQ

[JLogan3o13]

Hi, turbochugz, welcome to the forum. Is this an issue you've actually run into, or just a "what if" question? I've been repackaging MSIs for a very long time, and cannot recall ever having two different products with the exact same MSI name (different versions of the same product, maybe).

As bogQ mentions above, you can look at the attributes of the MSI file to confirm you're interacting with the one you want, or better yet use FileInstall to include the MSI in your script and remove the possibility of the script installing the wrong product.

[blademonkey]

sounds like an integrity question. Maybe using MD5sum could be useful to you?

this would ensure that a renamed binary of the same name would not be able to run unless the checksum matched that of the original, which isn't impossible, but it's less probable.

[turbochugz]

Thanks... Im not well versed in scripts and am currently reading the examples etc... Fileinstall() is definitely what i am looking for. Thanks for all the suggestions.

Edited August 22, 2012 by turbochugz