What packer would you use

im just curious to know what packer,
would you guys use if you were making
a program of your own?

[dyn!o]

It depends on what you would like to obtain:

- compression ratio (UPX)

- stability and compatibility (UPX / PeCompact)

- security (AsProtect / AcProtect)


Best regards,
dyn!o

nhoj,

your own packer. even if it isnt good as upx/asprotect, peoples wouldnt be able to use ready solutions for it

vecna

About security.....

dyn!o
Asprotect is no more secure (after release of stripper 2.07). Version 1.3 too (because of stripper 2.11 ). Maybe AcProtect is more secure, because it is not so popular. But it is low security now too.

SVKP is good, but I found only one serious program protected with it - TweakXP 3.

Xtremeprotector is very strong but it has a big minuses - 1) heavy code 2) rebooting if some debugger/decompiler dectected.

Other packers/cryptors are less secure.

[dyn!o]

Well, guys... I didn't want to learn anyone.

Anyway, let's see:

1. Own packer/crypter.
Developing own packer/crypter takes months. Even if you develop yourself an crypter within 6 months it will be easy to skip/unpack. To develop strong crypter you need minimum 2-3 persons and 1 year. And what? And I am still able to unpack it. So, where is the point of such a work?

2. AsProtect is no more secure.
That's interesting. With all respect to your skills and knowledge I bet you were always using Stripper and never unpacked AsProtect manually. Believe me, it is very good protector and if Alexy change few bytes then Stripper won't work and you wouldn't be able to quickly unpack it (I'm only assuming).

3. SVKP is good.
That's another interesting sentence. Probably you didn't saw the latest unpacker for SVKP.

4. AsProtect is more secure because of less popularity.
I propose to unpack latest Oxygen PM then (as a training).


Best regards,
dyn!o

no body has said fsg, smallest packer ever?
~190 byte loader this thing rocks

Originally Posted by mc707

About security.....


Xtremeprotector is very strong but it has a big minuses - 1) heavy code 2) rebooting if some debugger/decompiler dectected.

isnt that a good thing for security if somebody loads a debugger, then it will reboot? wont it make it slightly harder for the unpacker?

thanks guys for answering my first question.

next question on similar basis, can you use 2 packers on one program or would it not work?

also, if you had a packer, any packer doesnt matter which one, for example fsg or upx if you hex edited the code slightly, and the packer still worked, would that mean the person trying to unpack the program might not be able to do so using a normal unpacking program? would they have to do it manually?

sometimes you could use two protectors/packers on 1 program, but its just stupid and really doesnt add any security.

yes you can modify a packer to make it maybe harder to detect in PEiD/Foil Some Generic Unpackers, a generic oep cryptor was posted a while back that would do something like that, although it was quite unstable. It really wouldnt make programs any harder to unpack tho..

In regards to Xprotector, keep in mind you'll be rebooting your customers PC and the crackers PC so in the end your no farther ahead cause no one will want to buy your software. Altho to be fair to Xprotector, its optional if it reboots your PC or not but in any event programs run so slowly protected with it its useless.