Private Discussion on Helbreath Hack Development, (Do not release hacks which are talked about in here to the rest of the forum unless you write the hacks)
Once you downloaded that you can use a resource editor and change the way the password dialog shows up.. I use Resource Workshop and Microsoft C++ one
Once you changed the way you wanted it to look (you don't have too) you just run the passw.EXE file set the password on the dialog and set the password to a exe
>:[=
yep, it's the same one that I use for setting password on th tp hack, although I modified it to accept commandline parameters. I also modified a version to read the registry value in addition to password with different XOR value for the hack my friend use in cafe so that noob lamer can't steal the hack.
It's pretty neat coz you can add several layer of password on your exe after packing it using your prefered packer. But it is no use for protecting the exe from being dumped from memory & rebuild.
huhuhaha wrote: yep, it's the same one that I use for setting password on th tp hack, although I modified it to accept commandline parameters. I also modified a version to read the registry value in addition to password with different XOR value for the hack my friend use in cafe so that noob lamer can't steal the hack.
It's pretty neat coz you can add several layer of password on your exe after packing it using your prefered packer. But it is no use for protecting the exe from being dumped from memory & rebuild.
So I can use another packer to protect the source from being disassembled then run the password packer over it?
delinquent wrote: So I can use another packer to protect the source from being disassembled then run the password packer over it?
Yes. You can pack the exe using a packer/protector with anti memory dumping before protecting it using pepass. It usually means if they want a runnable copy of the exe from the memory dump, they will need to rebuild it manually. But it won't stop ppl from analyzing the code.
But for some commercial packer/protector such as aspack/asprotect, using password packer over it will not work.
delinquent wrote: So I can use another packer to protect the source from being disassembled then run the password packer over it?
Yes. You can pack the exe using a packer/protector with anti memory dumping before protecting it using pepass. It usually means if they want a runnable copy of the exe from the memory dump, they will need to rebuild it manually. But it won't stop ppl from analyzing the code.
But for some commercial packer/protector such as aspack/asprotect, using password packer over it will not work.
Yeah... but for ASProtect there are many strippers and stuff out there... So if someone really wanted to protect their source I doubt they would use it... I mean on the otherhand helbreath international needs to rethink all this stuff. They need to go back to the basics to solve this out but they won't do anything about it...
