PB strings in executeable

[Fred]

If you really want to do this, you won't probably rely only on strings but also compare bunch of code to compare with your 'signatures' to see if it's written in such or such langage. You can also write a C program with these strings in it, will it be a PB program then ? .

[PB]

> You can also write a C program with these strings in it, will it be a PB program then ?

Hehehe, good point -- I'll stick "MSVBVM60.DLL" and "AntiSmartCheck" in
my apps and maybe some losers will think it's a Visual Basic app that is
protected from SmartCheck... they'll then run SmartCheck and it'll report
"not a VB app" and they'll spend FOREVER trying to work out how the
app has hidden itself from SmartCheck.

Hmm... I think I'll actually do this with my apps -- it only adds a few bytes
to the exe and it's worth the hassle it inflicts upon any crackers. I could
even go as far as making my apps NOT run if MSVBVM60.DLL is missing,
but that's taking the illusion a little too far, I think. :roll:

Anyway, that's a really good idea you came up with, Fred... disguising our
apps with strings from other languages... it may actually work! Excellent!

(Edited to say "protected from" instead of "protected with").

[Straker]

@PB - That actually is a good idea.

I distribute a Derby database app but include MySql binaries and a Postgres driver just as red herrings since I have agressive competitors. Upon install I even install the Postgres driver even though it doesn't do anything.

If someone is trying to crack your code, might as well throw them a bone.

[thefool]

@shanara:

Haha who does look inside the exe anymore? We got tools to determine what compiler, packer, assembler, protector the developer used

And it doesnt really matter what language its in as long as it isnt compressed or protected in any way.