Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. COThank you so much Brickner !! I was exactly looking for this - processing the tcp payload (but I prefer C for learning). Can you please explain this line of your code : /* start of url - skip "GET " */ url = tcpPayload + 4; Why 4 ? And what should I explore to get more of such values (I read RFC for HTTP, but couldnt understand how to use it). I actually want to read all the HTTP data in that packet. Is it only possible if I reconstruct the full stream ? If yes, can you give me some idea over this reconstruction ? Thanks a lot !!
      singulars
    2. CO4 is for the "GET " - 3 ASCII characters + space. The RFC includes all of the possible requests names (like GET, POST...). If you only want the HTTP data in the single packet, then no reconstruction is needed. If you want the entire HTTP request, you might need to reconstruct the TCP stream (if the request is more than 1 packet). TCP reconstruction is another (and pretty complicated) issue and you should Google for it or open a different question. By the way, are you using LibPcap or the Windows wrapper WinPcap or is your question more generic?
      singulars
    3. COI am using libpcap on linux. I was aiming at capturing http packets and extracting some useful information, but reconstruction is undoubtedly too difficult for now. Should I target FTP, which contains just a code and message - is it feasible ? For eg. I would like to extract the username and password from FTP messages.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload