![]() |
|
|
|
#1
|
||||
|
||||
|
why do you want decompile a nullsoft install?
Tell us more information... If you want to get the password for a installation package, download the Nullsoft package (it's free) and study how it's implementing the input of the password and then uses a debugger on the API call's. |
|
#2
|
|||
|
|||
|
There are voices who tell that it's impossible. But this is not true at all: the truth is just that there isn't a nsis automatic decompiler out there.
This is what Scott told me: "You can't decompile an NSIS installer, at present, because the decompiler would have to understand all of the different types of binary headers from all of the different versions of NSIS, as well as know how to identify any of them that have had their source modified (since its open source), so, nobody has yet to write this psychic program." Honestly I think he's right, nobody would write such a general program, but everyone who is interested in reversing a nsis package should examinate the sources and understand how the installer is done. Well, the only thing that you should discover is the registry and/or config files modifications during the install process, because the files that are copied are clearly available to you after a complete installation, isn't it? So here's what I'd do, if I were you: I would extract all files simply installing the program on my HD; then I'd take trace of all config changes made during installation, including new or modified registry keys; finally I would use myself the NSIS installer package to re-package everything |
|
#3
|
|||
|
|||
|
Did you try InstallExplorer?
http://plugring.farmanager.com/downld/files/instexpl_v0.3.rar (needs FAR - http://farmanager.com/). It works quite well most of the time. |
|
#4
|
|||
|
|||
|
Nope. Won't work. Just tried it myself
|
|
#5
|
|||
|
|||
|
I'm afraid it's the only unpacker available. As I said, it works most of the time. But it won't handle protected files, especially since NSIS is open source and even contains a comment describing the lines you need to change to make an unpacker's life harder. But if you take the source, a debugger, and a disassembler, it might be possible to unpack the file.
|
|
#6
|
|||
|
|||
|
Sorry for reviving this old post, but this info can be useful to someone:
Most of the installers made with NSIS can be opened (and extracted) with 7ZIP. |
| The Following 2 Users Say Thank You to Molasar For This Useful Post: | ||
val2032 (01-28-2017) | ||
![]() |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| sys packer | emptyHook | General Discussion | 6 | 07-24-2012 19:46 |
| Another .NET packer | SystemeD | General Discussion | 5 | 09-19-2005 22:04 |
| First .NET packer? | SystemeD | General Discussion | 16 | 06-05-2005 15:15 |
| What packer would you use | Fade | General Discussion | 35 | 04-03-2004 12:01 |