Skip to content

Commit 9639b6d

Browse files
committed
renumber sections
1 parent 726d95e commit 9639b6d

File tree

1 file changed

+59
-58
lines changed

1 file changed

+59
-58
lines changed

systems.rst

Lines changed: 59 additions & 58 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
Chapter 9: Other Examples
1+
Chapter 7: Other Example Systems
22
============================
33

44
.. Assuming we keep a substantial set of examples, we should look
@@ -11,11 +11,10 @@ Chapter 9: Other Examples
1111
since new chapters are system focused.
1212
1313
Having focused on how to use the available cryptographic and
14-
authentication building blocks to secure the transport and network
15-
layers, we now turn our attention to other examples of how Internet
16-
systems are secured. The examples address specific threats—associated
17-
with specific use cases—that remain even when mechanism like TLS and
18-
DNSSEC are deployed.
14+
authentication building blocks to secure the transport layer, we now
15+
turn our attention to other examples of how Internet systems are
16+
secured. The examples address specific threats—associated with
17+
specific use cases—that remain even when TLS is deployed.
1918

2019
The systems described in this chapter are at different layers: some
2120
are are built into applications, some run at the IP layer, and some
@@ -38,7 +37,7 @@ algorithm; if one of your cryptographic algorithms turns out to be
3837
flawed, it would be great if your entire security architecture didn’t
3938
need an immediate redesign.
4039

41-
9.1 Pretty Good Privacy (PGP)
40+
7.1 Pretty Good Privacy (PGP)
4241
-------------------------------
4342

4443
Pretty Good Privacy (PGP) is an approach to providing authentication,
@@ -116,7 +115,7 @@ the application works can you make the right choices about which attacks
116115
to defend against (like forged email) versus which to ignore (like
117116
delayed or replayed email).
118117

119-
9.2 Secure Shell (SSH)
118+
7.2 Secure Shell (SSH)
120119
------------------------
121120

122121
The Secure Shell (SSH) protocol provides a remote login service,
@@ -254,15 +253,16 @@ the server, SSH first decrypts the contents and then “forwards” the
254253
data to the actual port at which the server is listening.
255254

256255
Port forwarding effectively creates a secure tunnel that provides
257-
confidentiality and authentication. (In practice, it sometimes also
258-
gets you through a corporate firewall, which often leave port 22
259-
open.) It is possible to provide a kind of virtual private network
260-
(VPN) using SSH tunnels in this way, but unlike the VPN mechanism
261-
described in the next section, SSH tunnels to a single remote machine
262-
rather than to a remote network. The latter gives you access to *any*
263-
machine on the local network.
264-
265-
9.3 IP Security (IPsec)
256+
confidentiality and authentication. It is possible to provide a kind
257+
of virtual private network (VPN) using SSH tunnels in this way, but
258+
unlike the VPN mechanism described in the next section, SSH tunnels to
259+
a single remote machine rather than to a remote network. The latter
260+
gives you access to *any* machine on the local network. In practice,
261+
it is also the case that corporate firewalls often block port 22 (SSH's
262+
well-known port) limiting the situations in which SSH works as a
263+
VPN-like tunnel.
264+
265+
7.3 IP Security (IPsec)
266266
-------------------------
267267

268268
One of the earliest efforts to integrate security into the Internet
@@ -271,7 +271,7 @@ called, is optional in IPv4 but mandatory in IPv6. Indeed, better
271271
security was one of the stated goals of IPv6, although it turned out
272272
that the central ideas could also be retrofitted into IPv4. It's also
273273
noteworthy that while the original intent was for IPsec to be part
274-
securing the network infrastructure (as discussed in the previous
274+
securing the network infrastructure (as discussed in the next
275275
chapter), today IPsec is most commonly used to implement secure
276276
tunnels running on top of the public Internet. These tunnels are often
277277
part of a Virtual Private Network (VPN), for example, connecting a
@@ -385,7 +385,7 @@ introduction to this section, a network of such tunnels can be used to
385385
implement an entire virtual private network. Hosts communicating over
386386
a VPN need not even be aware that it exists.
387387

388-
9.4 Web Authentication (WebAuthn) and Passkeys
388+
7.4 Web Authentication (WebAuthn) and Passkeys
389389
-----------------------------------------------
390390

391391
While public key cryptography has been well understood for decades,
@@ -528,7 +528,7 @@ sites. Those who have led their development hope that they start to
528528
replace the ubiquitous password for user authentication.
529529

530530

531-
9.5 Wireless Security (802.11i)
531+
7.5 Wireless Security (802.11i)
532532
---------------------------------
533533

534534
Wireless links are particularly exposed to security threats due to the
@@ -557,44 +557,6 @@ first-generation security algorithms—including Wired Equivalent
557557
Privacy (WEP)—that are now known to have major security flaws. We will
558558
focus here on 802.11i’s newer, stronger algorithms.
559559

560-
.. sidebar:: Securing Mobile Cellular Networks
561-
562-
*The other widely used wireless networking technology is the Mobile
563-
Cellular Network, today ubiquitously known as 5G. The biggest
564-
difference between 5G and Wi-Fi is that the Mobile Network Operator
565-
(MNO)—the counterpart of an enterprise network administrator—has
566-
more direct control over the devices that are allowed to connect to
567-
their network. Specifically, the MNO provides a Subscriber Identity
568-
Module (SIM) card that must be present in the mobile device. This
569-
SIM hosts a small database that includes a globally unique
570-
identifier (known as an IMSI, for International Mobile Subscriber
571-
Identifier) and a secret key.*
572-
573-
*When a device first becomes active, it communicates with a nearby
574-
base station over an unauthenticated radio channel. The base
575-
station forwards the request to a backend server over a secure
576-
backhaul connection, and that server (assuming it recognizes the
577-
IMSI) initiates an authentication protocol with the device. There
578-
are a set of options for authentication and encryption, but AES is
579-
commonly used. Note that this authentication exchange is initially
580-
in the clear since the base station to device channel is not yet
581-
secure. (The 5G specification uses significantly more precise
582-
terminology for all its components, but "backend server" conveys
583-
the basic idea; it is analogous to the AS used by Wi-Fi.)*
584-
585-
*Once the device and backend server are satisfied with each other's
586-
identity, the server informs the other 5G components of the
587-
parameters they will need to service the device (e.g., the IP
588-
address assigned to the device and the appropriate QoS
589-
parameters). It also instructs the base station to establish an
590-
encrypted channel to the device and gives the device the symmetric
591-
key it will subsequently use for the encrypted data channel with
592-
the base station. This symmetric key is encrypted using the public
593-
key of the device, so only the device can decrypt it. It does this
594-
using the secret key on its SIM card. Once complete, the device can
595-
use this encrypted channel to send and receive data over the
596-
wireless link to the base station.*
597-
598560
802.11i authentication supports two modes. In either mode, the end
599561
result of successful authentication is a shared Pairwise Master Key.
600562
*Personal mode*, also known as *Pre-Shared Key (PSK) mode*, provides
@@ -636,6 +598,45 @@ malicious AP. The end result of a successful authentication is a
636598
Pairwise Master Key shared between the wireless device and the AS, which
637599
the AS then conveys to the AP.
638600

601+
602+
.. sidebar:: Securing Mobile Cellular Networks
603+
604+
*The other widely used wireless networking technology is the Mobile
605+
Cellular Network, today ubiquitously known as 5G. The biggest
606+
difference between 5G and Wi-Fi is that the Mobile Network Operator
607+
(MNO)—the counterpart of an enterprise network administrator—has
608+
more direct control over the devices that are allowed to connect to
609+
their network. Specifically, the MNO provides a Subscriber Identity
610+
Module (SIM) card that must be present in the mobile device. This
611+
SIM contains a small database that includes a globally unique
612+
identifier (known as an IMSI, for International Mobile Subscriber
613+
Identifier) and a secret key.*
614+
615+
*When a device first becomes active, it communicates with a nearby
616+
base station over an unauthenticated radio channel. The base
617+
station forwards the request to a backend server over a secure
618+
backhaul connection, and that server (assuming it recognizes the
619+
IMSI) initiates an authentication protocol with the device. There
620+
are a set of options for authentication and encryption, but AES is
621+
commonly used. Note that this authentication exchange is initially
622+
in the clear since the base station to device channel is not yet
623+
secure. (The 5G specification uses significantly more precise
624+
terminology for all its components, but "backend server" conveys
625+
the basic idea; it is analogous to the AS used by Wi-Fi.)*
626+
627+
*Once the device and backend server are satisfied with each other's
628+
identity, the server informs the other 5G components of the
629+
parameters they will need to service the device (e.g., the IP
630+
address assigned to the device and the appropriate QoS
631+
parameters). It also instructs the base station to establish an
632+
encrypted channel to the device and gives the device the symmetric
633+
key it will subsequently use for the encrypted data channel with
634+
the base station. This symmetric key is encrypted using the public
635+
key of the device, so only the device can decrypt it. It does this
636+
using the secret key on its SIM card. Once complete, the device can
637+
use this encrypted channel to send and receive data over the
638+
wireless link to the base station.*
639+
639640
One of the main differences between the stronger AS-based mode and the
640641
weaker personal mode is that the former readily supports a unique key
641642
per client. This in turn makes it easier to change the set of clients

0 commit comments

Comments
 (0)