Easily Can Decode Nsis Files

hi guys
i find a way for decode exe file programs that write with nsis! and see all codes line by line!
is possible developers fix this problem?
If you do not believe give me exe file build with nsis and i give source code full!
thanks

you really need to start searching before posting such things. it's been known for years that 7-zip can extract things and get the script back (in a raw form). and the ways to prevent that from working have been clearly mentioned as well - searching is a skill which will help you.

Originally Posted by r2du-soft View Post

is possible developers fix this problem?

Who says this is a problem?

If some program is going to run on my machine I'd like the ability to inspect what it is doing/going to do to my system.

Even if we wanted to make it hard to decompile, it would still not be possible to prevent people from doing it because NSIS is open source. The only way to prevent it is to compile your own version of NSIS with a changed instruction order.

i think this is a weakness!
program must be compiled That in no way access to the source code it is not possible.
with access to source code Programmer labor lost. (this is mean).
im sorry for say this is a problem,but The issue is: (Security codes and programming efforts).
im searching but not found a topic for Prevent decode! is possible Put the address topics (thanks).
thanks

Why is it a weakness? Do you have anything to hide?




Even if you do this someone can still monitor your installer with Process Monitor or other types of monitoring tools and debuggers...

thanks guys
i have i idea for lock source code i think this way is the easiest way The existing methods.
we can change compress codec! in nsis we can compress file with : bzip2-lzma-zlib. if we write a new compress method when can locked source!
yours think this idea is bad?! or good!?

The official NSIS is not going to provide a new compression method that does not include the source, you would have to code that on your own but that is a lot more work than just changing the order of the enums in fileform.h.

working hard is that: packers can now pack nsis exe file! i test upx,ASPack .... .
after packing with this programs exe file becomes corrupted.
even after portable exe file again can decode and see source codes! 🙁

even if you prevent people seeing inside the script (which as has been mentioned can be worked around), it's not like what is being installed can't be decompiled anyway (and that based on your thing with the installer should be more of a concern to you than people getting at what's in the installer imho).

If you want to pack the stub then you need to use !packhdr. And of course there are tools out there to unpack these packers as well (For UPX just use upx -d app.exe). Packing the exe stub should only be used to reduce the size, not for "protection" from your users.

Can I just state the obvious? If you're using NSIS to write programs that aren't actually installers, then use a more general purpose language like C, C# or Visual Basic.

With a program that's open source, it's (almost) always possible to decode the binaries or the outputs of those binaries.

One of the things I do a lot of is tracking what installers do that have issues on modern systems to replicate with NSIS what the old installer is supposed to do. Pretty trivial task, regardless of what was used to write the installer. Once you know what it does, it is just a simple matter of writing an NSIS script that does the same thing with what ever additional compatibility fixes needed. One example of this is using a VM to track 16-bit installers on my x64 system to recreate a 32-bit installer with NSIS.

I would be very suspicious of the motives of anyone that wants to obfuscate what their installer does.