![]() In the meantime, if a large number of these requests had been hitting the server, it would eventually become overwhelmed and unresponsive. The server would wait for a pre-defined timeout period to discard the connection request. ![]() The server would expect a quick return from its acknowledgment but the attacker would not do so - or simply not respond. The receiving server would place this in a queue with identifying information, using a small amount of memory and resources to do so. An attacker would send an initial request (a SYN) asking for acknowledgment from the receiving server (an ACK). This is the same process as a SYN attack. ![]() Eventually the whole system would break down with no transactions occurring because the grocer is too busy trying to figure out who to service. He would probably wait a minute or two and call another number. However, imagine if a large number of customers took tickets and the grocer patiently started calling out numbers only to have no customers respond. The grocer notes what ticket number is to be serviced next, calls out that number, the customer answers and the transaction is begun. Any new customer is expected to pull a new, numbered ticket from the dispenser so the grocer can service the line-up of customers in an orderly fashion. The easiest way to describe how a SYN attack works is to think about your local grocer with the ticket system to serve customers at the meat counter.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |