Namrack: Resources

Below are some resources I use to gather information, as well as tools to get a job done. This paged is organized as follows:

Web Resources

Google: The search engine that is the foundation of all my information. Googling topics leads to more information, and there are a ton of resources about how to google better. Related to computer-specific searches, Google-fu (that is, your Google Kung-Fu capabilities) can be vastly improved by using their operators. You can tailor a search to find strings within a specific website, within all titles, etc. Such "Google hacking" information can be found in the Wikipedia page and in Google's Cheat Sheet. For non-computer related information, and just improving your efficiency with Google, check out LifeHacker's Google honing page. If you are bored and want to see some interesting Google "tricks" (such as making google do a barrell roll), you can find such fun at GoogleTricks.
Wikipedia:

Stealing the Network:
The Anti-Hacker Toolkit: This book lists a bunch of tools that ease gathering information about malware. As of typing, version 4 is not yet released; I would wait until this version comes out as the 3rd edition has a lot fairly dated software. The 3rd edition can be found with a quick Google search if you want to peruse the text before buying.
Digital Design and Computer Architecture:
ET's Reversing School: An excellent and easy to follow introduction into reversing (with beginning lessons focusing on Windows API calls from assembly). [Alternate Download Link]
Handbook of Applied Cryptography:

Inject your code into a Portable Executable file:
theForger's Win32 API Programming Tutorial:
Hiding NetCat Backdoor in an Installer: This video quickly demonstrates how to have an installer auto-run a file of your choice (in the case of the video, it was a script that shovels a windows shell) after the completion of a legitimate installation. The methods employed are easily detectable, but I intend to create a blog entry on how to take what m0j4h3d has done and expand it with detection-avoidance (both in the file itself and the services run after the file has executed).