Yep, I was partly replying to TheHive
(RTFM part) an partly to you (try the .ini file).
I wouldn't normally touch an app that dowloads "by his own will" something (which could be "any" payload
without really, really trusting the maker), but out of curiosity I tried it.
I used Recuva as it is a small enough app to quickly test.
I put the "Recuva Ninite Installer.exe" in a folder "C:\test_ninite"
I created in the same folder a sub-directory, naming it "NiniteCache" i.e.
Directory di C:\test_ninite
25/10/2009 16.24 <DIR> .
25/10/2009 16.24 <DIR> ..
25/10/2009 16.25 <DIR> NiniteCache
25/10/2009 16.10 169.160 Recuva Ninite Installer.exe
1 File 169.160 byte
It worked as expected, after the app finished I found in it a file named:
which can be opened with 7zip allright, the contents are similar to those of most installer packages, at first sight.
Uninstalling Recuva and re-running "Recuva Ninite Installer.exe" results in a new installation without re-downloading the files (MUCH faster).
Then I added a "ninite.ini" file with these contents:
and created a new directory "Recuva" inside the "NiniteCache".
was used nonetheless.
Then I renamed "NiniteCache" to "NiniteMyCache" and edited accordingly the "ninite.ini":
and re-ran "Recuva Ninite Installer.exe".
This time Recuva was re-downloaded and the resulting file "EA0A3E382F538A5BAD2E2A26FABEC2209E6880CA"
was inside the "C:\Downloaded\maanu\NiniteMyCache\Recuva\" folder.
Re-running "Recuva Ninite Installer.exe" results again in a "quick" install using local files.
So, though I would never use it in "real life", and I find it overall unneeded/unuseful
, it seems like it delivers to me
what it advertises.