What is this document about?
Later on in this document I will explain you why the difference between a senior developer and a cracker is so important to get a secured solution.
I will show you the different parts of product security and how they are connected to each over.
In fact there are a couple of really great solutions on the market I will show you.
I will guide you into the basic of the technology used currently; show you the weak points and biggest misunderstandings. I’m going to explain you why the combination makes you product secure….
Who should read it?
This document is dedicated to all of your developers, managers and development directors which need to deal with Anti cracking/hacking solution for they products.
Dieses Artikel beschreibt die verschiedene Projektmanagement Methoden mit denen ich in Berührung gekommen.
Ich versuche die Unterschiede und die gründe zu erforschen weshalb diese entstanden sind und in wie fern Sie immer noch eingesetzt werden oder nicht werden sollten.
Dies ist ein “WORK IN PROGRESS” entschuldigen Sie also mögliche Fehler.read more
Here you will find different Project i’m working on mostly including Sourcecode in different languages
Cracking ….so what is exactly the blog about?
“Software cracking is the modification of software to remove or disable features which are considered undesirable by the person cracking the software, usually related to protection methods copy protection / executable protection, trial/demo version, serial number, hardware key, date checks, CD check or software annoyances like nag screens and adware” Wikipedia
So as a research i will try to break and bypass security systems document my work and public it, i will try to show you why there is a security hole and also how to avoid it.
This is a Blog so feel free to comment, ask (help me with my English) what ever