@@ -34,15 +34,15 @@ but they generally must look at packet headers, which contain
3434destination information, to determine where to
3535send traffic.
3636
37- The second major requirement is *integrity *, which about having
37+ The second major requirement is *integrity *, which is about having
3838confidence that the information we're receiving is trustworthy, and
3939for example, has not been modified by some adversary while in
40- transit. Assuring integrity is multi-faceted, involving far more than
41- "in transit" adversaries.
40+ transit. Assuring integrity is multi-faceted, involving more than
41+ just "in transit" adversaries.
4242
4343For example, we need to be able to verify that an item of data was
4444sent by the entity that claimed to have sent it. This means we need to
45- *authenticate * the sender, and in the example of e-commerce, this is
45+ *authenticate * the sender. In the example of e-commerce, this is
4646what allows us to know we are connected to, say, the website of the
4747vendor we wish to patronize and not handing over our credit card to
4848some impostor.
@@ -60,9 +60,9 @@ account holder?
6060Integrity also requires messages be *original * and *timely *, which is
6161threatened by the possibility data is captured and then retransmitted
6262at some later time. This is known as a *replay attack *, where for
63- example, we want to protect against an item being repeatedly added to
64- a shopping cart by an attacker . Thus, it is a common requirement to
65- have some form of *replay prevention *.
63+ example, we want to protect against an attacker repeatedly adding an
64+ item to a shopping cart. Thus, it is a common requirement to have some
65+ form of *replay prevention *.
6666
6767The final major requirement is *availability *, which is primarily
6868concerned with protecting networks and the systems attached to them
0 commit comments