There are two ways to write a book about computer hacking. The first is to write an encyclopedic account of every known system and its dialup numbers, passwords, loopholes, and how to increase one's access once inside. There is nothing particularly wrong with this approach except that by publication time much of the contents will likely be out-dated. And surely, after word leaks to the computer sites of the world the remaining information will be rendered nonfunctional. Such a specific approach, while exciting, is best left to periodicals,
which can keep readers updated on the constantly changing security frontier. Indeed, there are both print and on-line publications which attempt to do just that. The second way to write a book about computer hacking is to write an encyclopedic account of the methods by which security is breached and systems penetrated.
This is a much more agreeable solution to the problem of how to distribute changing information. The readers of such a book can then follow those methods, those algorithms, add some of their own creativity, and will never end up facing a situation drastically different from the ones the text has prepared the hacker to encounter.
Naturally, way-to-write-a-book Number Two is the way this book has been written. At some points during the course of writing this book I've found that to talk about certain information requires knowledge of another aspect of hacking entirely. I tried to keep this book flowing in a logical order, conducive to understanding, but occasionally you will find ripples in the flow. If you come across a term or situation that the book hasn't yet prepared you for, forget about it. You'll learn soon enough. Or look in the glossary you might find the answer you seek there. Computer hacking is a subject which contains a voluminous amount of information. Repeatedly, as I prepared the manuscript, I had to decide whether or not to go into great detail in a particular area, or allow you to discover certain inside tricks on your own. Sometimes I compromised, sometimes I didn't. Some things I left out because they were too scary. When all is said and done, the important part isn't the writing of the book, it's the reading of it, and the actions that result from the reading. Hacking is about doing something, for yourself and on your own. It's not about reading about doing something. I will gladly point you in the right direction, but I won't be your guide once you're on your way. Speaking of books being read, it is often a wonder that they ever do get to that readable finished state at all. Thank you R.S. and j for critiquing selections from this book; thanks to the people at Loompanics for recognizing that the Constitution
does, after all, allow freedom of the press; and to the many hackers and crackers who offered suggestions: Morris, Janet, Sex Pack, Carl Fox and the happy Gang Of Demon Street.
