Operating Systems and Web Security: Fall 2012: Difference between revisions
| Line 358: | Line 358: | ||
</td> | </td> | ||
<td> | <td> | ||
<p>Felt et al., [https://www.eecs.berkeley.edu/~daw/papers/perms-webapps11.pdf The Effectiveness of Application Permissions] | <p>Felt et al., [https://www.eecs.berkeley.edu/~daw/papers/perms-webapps11.pdf The Effectiveness of Application Permissions]<br> | ||
Lie & Litty, [http://sites.google.com/site/lionellitty/research/publications/STC10.pdf Using Hypervisors to Secure Commodity Operating Systems] | Lie & Litty, [http://sites.google.com/site/lionellitty/research/publications/STC10.pdf Using Hypervisors to Secure Commodity Operating Systems] | ||
</p> | </p> | ||
| Line 377: | Line 377: | ||
</td> | </td> | ||
<td> | <td> | ||
<p>Belay et al., [http://www.scs.stanford.edu/~dm/home/papers/belay:dune.pdf Dune: Safe User-level Access to Privileged CPU Features] | <p>Belay et al., [http://www.scs.stanford.edu/~dm/home/papers/belay:dune.pdf Dune: Safe User-level Access to Privileged CPU Features]<br> | ||
McCune et al., [http://www.cs.purdue.edu/homes/bertino/426Fall2009/flicker.pdf Flicker: An Execution Infrastructure for TCB Minimization] | McCune et al., [http://www.cs.purdue.edu/homes/bertino/426Fall2009/flicker.pdf Flicker: An Execution Infrastructure for TCB Minimization] | ||
</p> | </p> | ||
| Line 396: | Line 396: | ||
</td> | </td> | ||
<td> | <td> | ||
<p>De Groef et al., [https://lirias.kuleuven.be/bitstream/123456789/354589/2/fp015-degroef.pdf FlowFox: a Web Browser with Flexible and Precise Information Flow Control] | <p>De Groef et al., [https://lirias.kuleuven.be/bitstream/123456789/354589/2/fp015-degroef.pdf FlowFox: a Web Browser with Flexible and Precise Information Flow Control]<br> | ||
Wang et al., [http://www.usenix.org/event/sec09/tech/full_papers/wang.pdf The Multi-Principal OS Construction of the Gazelle Web Browser] | Wang et al., [http://www.usenix.org/event/sec09/tech/full_papers/wang.pdf The Multi-Principal OS Construction of the Gazelle Web Browser] | ||
</p> | </p> | ||
| Line 415: | Line 415: | ||
</td> | </td> | ||
<td> | <td> | ||
<p>Mickens & Dhawan, [http://research.microsoft.com/pubs/154698/Atlantis-SOSP.pdf Atlantis: Robust, Extensible Execution Environments for Web Applications] | <p>Mickens & Dhawan, [http://research.microsoft.com/pubs/154698/Atlantis-SOSP.pdf Atlantis: Robust, Extensible Execution Environments for Web Applications]<br> | ||
Chen et al., [http://www.collinjackson.com/research/papers/appisolation.pdf App Isolation: Get the Security of Multiple Browsers with Just One] | Chen et al., [http://www.collinjackson.com/research/papers/appisolation.pdf App Isolation: Get the Security of Multiple Browsers with Just One] | ||
</p> | </p> | ||
| Line 435: | Line 435: | ||
<td> | <td> | ||
<p>Chen et al., Overshadow: A Virtualization-Based Approach to Retrofitting | <p>Chen et al., Overshadow: A Virtualization-Based Approach to Retrofitting | ||
Protection in Commodity Operating Systems | Protection in Commodity Operating Systems<br> | ||
Andrus et al., Cells: A Virtual Mobile Smartphone Architecture | Andrus et al., Cells: A Virtual Mobile Smartphone Architecture | ||
</p> | </p> | ||
| Line 454: | Line 454: | ||
</td> | </td> | ||
<td> | <td> | ||
<p>Akhawe, Saxena, & Song, Privilege Separation in HTML5 Applications | <p>Akhawe, Saxena, & Song, Privilege Separation in HTML5 Applications<br> | ||
Tang et al., CleanOS: Limiting Mobile Data Exposure with Idle Eviction | Tang et al., CleanOS: Limiting Mobile Data Exposure with Idle Eviction | ||
</p> | </p> | ||
Revision as of 06:25, 3 November 2012
Course Outline
The outline of the course can be found here.
Reading Responses
In general, reading responses should be turned in by 8 PM on Monday prior to the associated readings being discussed in class. Submitted reading responses should be no more than 1000 words in total for discussion of all the week's readings. (NOT 1000 words per reading!) Reading responses should be a discussion of what you got out of the readings and what questions you still have. I will attempt to read everyone's responses before class so I have an idea how to direct in-class discussion. In particular, I will be looking for topics on which to give more background.
Suggestion on how to do responses: Read all the papers first, then take a break, then write a response. Don't write after each reading. You don't even need to take notes unless that is how you read papers.
The first reading response is due on Monday, September 17th, 8 PM. Note that this response should also discuss how useful and enjoyable the unsupervised in-class discussion of the readings went.
Responses should be submitted via Carleton's new cuLearn.