Talk:Reverse Engineering/Computer Networks

Network Protocols
For the section on Network Protocols, Ethernet/IP/PPP info is bulleted. However, it seems to me there are at least 2 major aspects to protocol reverse engineering. One would be analysis of the Ethernet/IP/PPP headers. Another is the reverse engineering of the contents themselves, which is much like proprietary file format engineering. I'd like to see both ideas here, but I'm not sure how best to do it.

Contents reverse engineering could include info on common ways to package data, things like headers, bytecounts, checksums, crcs, as well as info on endian-ness.

Also information on compression and encryption is relevant.

Commonly used protocols and ways of encoding contents could be discussed. RPCs, XML, XML/RPCs.


 * What I was thinking originally when i created this page was simply protocol reverse engineering. For instance, the GAIM project had to reverse engineering the AIM protocols, so that GAIM users could communication with AIM users, etc... We can really go as in-depth as we want to however, just add any bullets to the outline that you think are appropriate! -- 16:07, 4 December 2005 (UTC)


 * Thanks, I'm thinking some case studies could drive the general discussion. Would be interesting to contact people involved with GAIM, SAMBA, or other projects to see if they would want to contribute.  --Kenlars99 20:21, 4 December 2005 (UTC)


 * Exactly, the more people the merrier. I'm going to be focusing most of my attention in the comming days to the Reverse Engineering/Anti-Reversing chapter, because i have a few books on that subject laying around, and can get to work on it quickly. However, we can do a lot on this topic as well, so all the help we can get, the better. -- 14:46, 5 December 2005 (UTC)