What hackers learn that the rest of us don't

IEEE Security and Privacy

Volumn 5, Issue 4, 2007, Pages 72-75

  Bratus, Sergey ^a  

^a DARTMOUTH COLLEGE   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

COMPUTER HARDWARE; INFORMATION TECHNOLOGY; REVERSE ENGINEERING; SECURITY OF DATA;

HARDWARE MODIFICATION; MALICIOUS ATTACKS;

COMPUTER CRIME;

EID: 34547995670     PISSN: 15407993     EISSN: None     Source Type: Journal    
DOI: 10.1109/MSP.2007.101     Document Type: Article

References (10)

1. J. Koziol et al., The Shellcoder's Handbook: Discovering and Exploiting Security Holes, Wiley, 2004.
2. G. Conti, "Why Computer Scientists Should Attend Hacker Conferences," Comm. ACM, vol. 48, no. 3, 2006; www.rumint.org/ gregconti/publications/20050301_CACM_HackingConferences_Conti.pdf.
3. J.R. Levine, Linkers and Loaders, Morgan Kaufmann, 2000.
4. Phrack, vol. 58, article no. 8; www.phrack.org.
5. J.B. Rosenberg, How Debuggers Work: Algorithms, Data Structures, and Architecture, Wiley, 1996.
6. K. Kaspersky, Hacker Debugging Uncovered, A-List, 2005.
7. M. Schiffman, Building Open Source Network Security Tools: Components and Techniques, Wiley, 2002.
8. M. Gregg, Hack the Stack: Using Snort and Ethereal to Master the 8 Layers of an Insecure Network, Syngress, 2006.
9. Aleph One, "Smashing the Stack for Fun and Profit," Phrack, vol. 7, no. 49, 1996.
10. G.E. McGraw and G. Hoglund, Exploiting Software: How to Break Code, Addison-Wesley, 2004.