Fernando Gont wrote:
I listened to the podcast and got the idea that the socket is in
ESTABLISHED state (so after 3 way handshake) and they
mention that a packets PCB resources have timers, and that is what they
exploit. Perhaps you establish the session and
send an HTTP request (pretend it's http) and never ACK the answer that
gets repeated based on the internal timers. It seemed to me they say
that some stop repeating their content and just die.
-p
| Greg Kroah-Hartman | [PATCH 005/196] Chinese: add translation of SubmittingDrivers |
| Christian Kujau | 2.6.20.4: NETDEV WATCHDOG and lockups |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Jack Steiner | Re: [patch] my mmu notifiers |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Arjan van de Ven | Re: [GIT]: Networking |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Jens Axboe | Re: [BUG] New Kernel Bugs |
| YAMAMOTO Takashi | removing VOPs |
| Lennart Augustsson | Re: FreeBSD 5/6/7 kernel emulator for NetBSD 2.x |
| Daniel Carosone | Re: direct I/O |
| Brian Buhrow | Re: /sbin/reboot and secmodel |
