@@ -224,10 +224,13 @@ \section{Past experiments}
224
224
requiring no additional action by the user to enable.
225
225
226
226
While both Flash and Java Applets provided ways to interact with JavaScript and
227
- the webpage, the primary way for a user to interact with both were via the
228
- plugins' embedded object within the page, resulting in a poor user experience.
229
- WebAssembly, by contrast, does \textit {not } have its own way of interacting with
230
- the user.
227
+ the web page, the primary way for a user to interact with both were via the
228
+ plugins' embedded objects within the page.
229
+ This disconnect between the web page and the application resulted in a jarring
230
+ disintegrated experience for users, and poor or nonexistent accessibility by
231
+ default for screen readers.
232
+ WebAssembly, by contrast, does \textit {not } have its own way of interacting
233
+ with the user---all input and output is performed using the JavaScript bridge.
231
234
While WebAssembly does require its own execution environment
232
235
similarly to Flash and Java Applets, on the Web this environment is intertwined
233
236
heavily with existing JavaScript engines.
@@ -251,16 +254,13 @@ \section{Past experiments}
251
254
252
255
Finally, as previously mentioned, WebAssembly was designed with major goals of
253
256
high performance and security.
254
- While Java applets could offer high performance, their reliance on the JRE on
255
- the host system has both performance and security implications.
256
- Flash, on the other hand, suffers from poor performance as well as introduces
257
- a greater security risk.
258
- % TODO: Reference some performance studies
259
- In both cases, integrating with another piece of software introduces new
260
- potential vectors for attackers to exploit---the larger the attack surface
261
- creates more opportunities for software bugs to result in security
262
- vulnerabilities.
263
- % TODO: Link some vulnerabilities
257
+ While Java applets and Flash applications can offer high performance in optimal
258
+ circumstances, their reliance on software installed on the host system has
259
+ security implications.
260
+ Integrating with another piece of software introduces new potential vectors for
261
+ attackers to exploit---the larger the attack surface creates more opportunities
262
+ for software bugs to result in security
263
+ vulnerabilities\cite {JRECveDetails ,FlashSecurityUpdates }.
264
264
Security researchers\cite {Pwn2OwnMillerInterview } and the \citeauthor {CISASecuringWebBrowser }\cite {CISASecuringWebBrowser } suggest
265
265
disabling such plugins in order to increase security.
266
266
0 commit comments