#16
|
||||
|
||||
Peleon: "shareware authors can do a lot more from his source code like that encryption scheme that you talked about"
Very, very, very wrong my friend. First of all shareware and commercial authors have no clue how crackers work and which tools they use. Even if some of them know what tools crackers use then it would take them long years to defeat them (tools) and every day new tools are developed. I saw a lot of protected software in which the protection was "messed" and doubled sever times - for me it was obvious that it tooks a lot of time to design and test it but usually it took me no more than 20 minutes to defeat them, not because I am masta cracka but because the protection was not tested (by crackers). Tell an company to implement 1000 protections in their software and that won't change the fact that it would take few minutes to break it. What are the best protections? The one made by crackers - it is and will be a rule, always. Look at PeLock, Obsidium, AsProtect, AcProtect, etc. - they were made by crackers and beat every dongle and own commercial/shareware protections. About JMI idea. I agree totally. I will give you (Peleon) an example: 1. I am protecting an app. 2. I am crypting the code between 401234 - 404321 with my private RSA-1024 key. 3. Now I am generating hardware dependent licence files for every my customer which is connected with HDID+PubKey. 4. The software will run only with the proper key. How would you crack the sofware without LEGAL key bought for YOUR machine? If you won't buy the key - It's impossible. As you see carefully implemented software protection based on a cryptography gives you a lot better protection. Add some anti-*, anti-* and you have the strongest possible protection. Remember: the most simpliest ideas are the most strongest. Peleon: I don't want to learn or beat you. With all respect to your person (skilled for sure) I'm probably a little older man and that's why I've allowed myself to take a word in this discussion. Please learn from it and don't get offended. I left all the coments for you guys... It's very deep topic... dyn!o Last edited by dyn!o; 05-12-2004 at 15:46. |
#17
|
|||
|
|||
Hi dyn!o, of course, not offended here Thanks a lot for the information. Indeed, lots to think about this subject cos it looks promising
Didnt know that Alexey (asprotect) was a cracker Regards |
#18
|
||||
|
||||
Yesterday I thought I know much. Today I think I knew very little. Tomorrow I will be sure I didn't knew anything.
Think about it . dyn!o |
#19
|
|||
|
|||
I'm old enough to have learned that I have alot to learn.
Regards,
__________________
JMI |
#20
|
|||
|
|||
The word of a old cracker
I think is resumed in this:
If the program (or part of a program) run in my machine (one time, two times, n times), is always crackeable, if not run in my machine can be crackeable or not, and will be very difficult. I think ORC say this (is not literal or exact) Ricardo Narvaja |
#21
|
||||
|
||||
That's the point.
|
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
PE Loader Questions | dila | General Discussion | 13 | 12-20-2011 12:03 |
2 questions about hasp | suddenLy | General Discussion | 3 | 01-12-2005 01:51 |
2 questions (IDA / Windows 2k/2k3) | skyper | General Discussion | 8 | 04-22-2004 08:44 |
some unpacking questions | gnasher | General Discussion | 2 | 01-03-2004 20:44 |