mirre-mt/masters-thesis
Archived
1
0
Fork 0
Code Releases 1 Activity

tex: edit stuff in complexity

Browse Source
This commit is contained in:
leo 2023-05-25 04:08:10 +02:00
parent 63772b124e
commit 0da94ed5d0
Signed by: wanderer
SSH Key Fingerprint: SHA256:Dp8+iwKHSlrMEHzE3bJnPng70I7LEsa3IJXRH/U+idQ
1 changed files with 13 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
tex/text.tex
View File

@ -336,20 +336,21 @@ internet is no easy task.
\n{3}{Complexity}
Browsers these days are also quite ubiquitous programs running on
\emph{billions} of consumer-grade mobile devices (which are also notorious for
\emph{billions} of consumer grade mobile devices (which are also notorious for
bad update hygiene) or desktop devices all over the world. Regular users
usually expect them to work flawlessly with a multitude of network conditions,
network scenarios (café WiFi, cellular data in a remote location, home
broadband that is DNS-poisoned by the ISP), differently tuned (or commonly
misconfigured) web servers, a combination of modern and \emph{legacy}
encryption schemes and different levels of conformance to web standards from
both web server and website developers. Of course, if a website is broken, it
is the browser's fault. Browsers are expected to detect if \emph{captive
portals} (a type of access control that usually tries to force the user through
a webpage with terms of use) are active and offer redirects. All of this is
immense complexity and the combination of ubiquity and great exposure this type
of software gets is in the authors opinion the cause behind a staggering amount
of vulnerabilities found, reported and fixed in browsers every year.
network scenarios (the proverbial café WiFi, cellular data in a remote
location, home broadband that is DNS-poisoned by the ISP), differently tuned
(or commonly misconfigured) web servers, a combination of modern and
\emph{legacy} encryption schemes and different levels of conformance to web
standards from both web server and website developers. Of course, if a website
is broken, it is the browser's fault. Browsers are expected to detect if
\emph{captive portals} (a type of access control that usually tries to force
the user through a webpage with terms of use) are active and offer redirects.
All of this is immense complexity and the combination of ubiquity and great
exposure this type of software gets is in the authors opinion the cause behind
a staggering amount of vulnerabilities found, reported and fixed in browsers
every year.
\n{3}{Standardisation}