Csc5113c May 2026

One week you’re coding a reliable data transfer protocol over UDP (think: TCP from scratch, but sadder). The next week, your lab partner is tasked with launching a selective ACK dropping attack against your implementation using Scapy.

Since course codes vary (e.g., University of Oklahoma’s CS/IT sequences), I have framed this around the spirit of an advanced, project-heavy networking/security course. By a Survivor of CSC5113C csc5113c

One student famously found a delayed SQL injection spread across 47 fragmented ICMP echo requests. The professor didn’t even know that was possible until the student presented it. "Don't trust the wire. Don't trust the endpoint. Don't trust your textbook." This isn't paranoia. It’s the course’s core thesis. The Internet was built on trust. Modern networks survive on verification. One week you’re coding a reliable data transfer

I was debugging a "simple" TCP congestion control algorithm for my CSC5113C project. The assignment was straightforward: modify the Linux kernel’s TCP stack to improve throughput over high-latency links. Straightforward, until it wasn't. By a Survivor of CSC5113C One student famously

There is a moment in every Computer Science graduate course where the textbook stops making sense and reality kicks in. For me, that moment came at 2:00 AM in the networking lab, watching Wireshark scroll by like the green code from The Matrix .

CSC5113C does something crueler—and far more educational. It forces you to implement the protocols, then immediately break them.