Visual Basic Program Protection

[rabbit]

That's what I meant.

[Networks]

I used to do that, but Newby kept screaming at me like "I'LL JUST UNPACK IT!!"  That combined with me not caring that much, I stopped packing.  It was just an extra step in my release process.  Although, for some of my larger programs (the beastly 2meg FoFoBot), doing a upx brought that down to a nice 800kb.

Or use a commercial packer that isn't as popular? Find a packer that doesn't also have an immediate unpacker. In other words do some research on your packer at least. There are numerous code obfuscation techniques that you can use beside a packer though.

[rabbit]

Another solution is to just go open source

[TheMinistered]

Or... you could... go out on a wiiiide branch... and write your own packer? ;p like omg! why didn't I think of that?  That way... they need knowledge of asm and how packers work...

[Newby]

If you used a hash-based authentication (translate the password into a hash and compare it with the hash so all they see is the hash value when they disassemble it) I bet they'll give up.

One byte in a hex editor.

Eww, I forgot about that. Wow. :O

[MysT_DooM]

I've decided to implement the hardware based auth, seems like the best one.

[rabbit]

One byte in a hex editor.

[Tazo]

One byte in a hex editor.

Then why don't you tell him how to do it instead of making useless posts like that? You obviously know, tell.

[Networks]

God just use that auth and find some commercial packer like SoftComp and I am sure you'll be fine.

[rabbit]

One byte in a hex editor.

Then why don't you tell him how to do it instead of making useless posts like that? You obviously know, tell.

It's been said before: pack it.  Just about every check that can be done from VB is pretty much "IF x Then Y", where all you have to do is change je to jne.  It's pretty blatant if you've read the entire thread.

[Joe[x86]]

How not to protect your program.

[rabbit]

Joe, that wasn't protected at all.