XHEO Lic./.NET Reactor/IntelliLock Cracking serials

[xploid]

Hey,

i saw that you already have had some success on reverse engineering Assemblies protected by the 3 Programs i mentioned in the topic.

So when you can reengineer the code, then you should be able to bypass the licensening right? XHEO Pack costs many thousands of $ and there are still people who can crack that? Why are people spending so much money on programs which are cracked so fast?

So can anyone tell me if there are people out there who can crack all 3 licensening programs? I just want to know if there are any.

[RapidCrash]

Why do you need to know?

As for why people pay so much money, it's called advertising. People want to feel like their software is safe and secure, and that's what the program targets. "People have been able to crack the competitor's programs, but our protects your and they cannot crack ours" is pretty much all they tell people. Now do remember these aren't the people that would go looking around for ways to crack the programs, so they will consider the "best choice" and purchase one. 'Nuff said.

[xploid]

I wrote an application as a student research project. To be more specific its a usenet downloader and i want to sell the program for a small amount to get something back. there will be a long trial period to make sure a customer can decide if its an application which he likes or not.

so i was asking me if i should "protect" my application with .net reactor/intelli lock or for a bit more money with xheo stuff. if i would choose xheo then i want to be sure that it is a secure way for the money. but it seems not. its a lot of money for a student the hole xheo thingy...

im just unsure which protection i should choose. thats why i asked here. regarding the other posts there are some cracks arround here

there are some open source parts in my application but also some which i'd like to hold closed source. but thats hard in a .net assembly...

[Kurapica]

Let me tell one little fact, the only type of applications crackers are not usually interested in is open source type.

If I were you I would not use any protection, If you run then you are gonna just die tired !! so I will simply leave the application as is and let people see the code in reflector, you should use a shareware distribution plan but without any limitations or restrictions, If any body likes the software he or she will donate and you probably will get some cash.

buying Xheo or .NET reactor will make your code slower and it will attract more crackers too !

I only use names obfuscation in tools to make it harder alittle bit for developers of protections to find out how the tool works, but If anybody I trust asks me for the source I will give it without hesitation.

Remember that .NET is supposed to be reflected and that's one of the purposes of the framework.

good luck.

[tribal]

With xheo licensing you mean this? The whole validation etc is done from a dll and cracking it is as simple as writing your own implementation with all the functions called by the program using the licensing, signing your dll and patching the program to accept your dll instead of theres.

You could probebly use the cheapest licensing availible that suites your needs, if someone wants to crack it it gets cracked, as simple as that.

[keng]

xploid says it!
all those programs with deploylx.licensing dlls are incredibly easy to crack to bits...