cs161-staff / textbook

Online textbook for CS 161: Computer Security at UC Berkeley.
https://textbook.cs161.org/
56 stars 16 forks source link

Minor edits suggested by student #40

Closed peyrin closed 5 months ago

peyrin commented 1 year ago

A former student sent these to cs161-staff@berkeley.edu. I have not checked the correctness/validity of these edits, but putting them here for later.

In the section on tradeoffs between TCP and UDP, there's a sentence that ends "it will wait indefinitely for dropped packets to resent." I think this should end in "to be sent again."

In the DDoS section, one sentence starts with "Despite this however, DoS." I would either add a comma after "Despite this" or abbreviate this to "However, DoS."

In the section on the disadvantages of firewalls, I would change "As a result firewalls are becoming increasingly less effective." to "As a result, firewalls are becoming less effective."

In the application-level DoS section, it's a bit confusing to include a specific example without introducing it as an example.

Possible implementations of this are that you could limit each user to 4 GB of RAM and 2 CPU cores or you could ensure that only trusted users can execute expensive requests. Another possible “defense” could include proof-of-work (like a CAPTCHA) wherein you force users to spend some resources in order to issue a request.

I would consider rephrasing this part. Perhaps you could say, "One way to implement this would be to place specific limits on each user, such as 4 GB of RAM and 2 CPU cores. One could also place different limits on different users, so only trusted users could execute expensive requests. Another possible “defense” strategy would be proof-of-work (like a CAPTCHA), wherein you force users to spend some resources in order to issue a request." Also, the proof of work idea seems a bit different from quotas, so I would more clearly relate the two ideas or move the sentences about proof of work into a new paragraph.