![]() ![]() Unfortunately, it isn't tested for installers with more command line parameters. Thats one reason software authors use obfuscators - to prevent others from reverse-engineering their code and to protect their intellectual property. The project extraction recreate the folders "Common" and "PRJ1" on the desktop (just modify the script as needed. Net reflector from ' If someone ran an obfuscator (such as Dotfuscator) on the code, though, all bets are off. There is only a small bit of size increasing, because the files you are using inside the installer will not be added again. This causes all the files in "Common" and in "PRJ1" (even subdirs) to be included in the installer. I simply start my script with these lines: Where PRJ1, PRJ2 are the names of my project (and also the "filename" portion of my installer) I'm using the following directory structure: The backup can be extracted using the "/source" switch in the command line of the installer. nsi script called "AutoBackup" for keeping a backup of the entire project inside the project himself. That leaves one possibilty, the compiled NSI script. ![]() I have searched this board and found no false alerts regarding version 1.1g (well none for any version actually!), so its most likely that the 1.19 bootstrap/header is not the cause. Also the packaged files in the intaller (after compression) would not likely cause the false trigger as the virus is detected in both the installer and uninstaller by NOD32. The files inside the package are definately not to blame as they are just a series of text files once installed (and they pass all scans once decompressed). NOD32 Virus scanner (from identifies the virus in both the installer and uninstaller, however Norton Antivirus does not. Some guy reckons that a package put together with NSIS (which was downloaded from a highly-visited site) contains a virus (Win32/DelAll). īTW: Modifying the NSIS source codes and "randomizing" some of it's data structures would be one method of obfuscation.Heres another situation where it would come in handy: This cannot be prevented without special hardware mechanisms (like a TPM), it can only be made more difficult by using techniques of "obfuscation". Guess why those new "unbreakable" Copy Protection systems like AACS (Blue Ray Disc) have been broken that fast! They didn't crack the protection itself, they simply grabbed the "secret" keys from memory while playing the disc in a legitimate player. So somebody could do a memory dump and obtain your string. But even if you mange to keep your key a secret (the key must be stored somewhere in the EXE file too), still the string would be in memory at runtime. Of course you could try to encrypt the string and decrypt it at only at runtime. You cannot protect strings! If your installer "knows" (uses) the string, then it must be stored somewhere in the EXE file. Only thing I was afraid was strings (which are in disassembly). Nsis Decompiler How To Do Some NSIS is script-based and allows you to create the logic to handle even the most complex installation tasks. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |