|
|
| Line 300: |
Line 300: |
| </td> | | </td> |
| <td> | | <td> |
| <p> | | <p>Old APIs |
| </p> | | </p> |
| </td> | | </td> |
| <td> | | <td> |
| <p> | | <p>Bright, [http://arstechnica.com/features/2012/10/windows-8-and-winrt-everything-old-is-new-again/ An in-depth look at WinRT] |
| </p> | | </p> |
| </td> | | </td> |
Revision as of 22:54, 21 October 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.
Readings
|
Date
|
Topics
|
Readings
|
Notes
|
|
Sept. 6
|
Introduction
|
|
Introduction Notes
|
|
Sept. 11
|
Fundamentals (Groups)
|
Saltzer & Schroeder, The Protection of Information in Computer Systems (1975)
(Link to PDF version)
|
Fundamentals Notes
|
|
Sept. 13
|
Criteria (Groups)
|
The DoD Orange Book (1985)
|
Criteria Notes
|
|
Sept. 18
|
Fundamentals (Discussion)
|
|
|
|
Sept. 20
|
Criteria (Discussion)
|
|
|
|
Sept. 25
|
Code Injection Attacks
|
Aleph One, Stack Smashing for Fun and Profit
Buchanan et al., When good instructions go bad: generalizing return-oriented programming to RISC (proxy)
|
Code Injection Attacks Notes
|
|
Sept. 27
|
Code Injection Defenses
|
Bojinov et al., Address space randomization for mobile devices (proxy)
Kc et al., Countering Code-Injection Attacks With Instruction-Set Randomization (proxy)
OPTIONAL: Barrantes et al., Randomized instruction set emulation (proxy)
|
Code Injection Defenses Notes
|
|
Oct. 2
|
Cross-Site Scripting
|
CERT, Malicious HTML Tags
Wikipedia, Cross-Site Scripting
OWASP, Cross-Site Scripting (XSS)
Gundy & Chen, Noncespaces: Using Randomization to Enforce Information Flow Tracking and Thwart Cross-Site Scripting Attacks
|
Cross-Site Scripting Notes
|
|
Oct. 4
|
Web Mashups
|
Jackson & Wang, Subspace: secure cross-domain communication for web mashups
Wang et al., Protection and communication abstractions for web browsers in MashupOS (proxy) (author)
|
Web Mashups Notes
|
|
Oct. 9
|
L4
|
Liedtke, Toward Real Microkernels (proxy)
Klein et al., seL4: formal verification of an OS kernel (proxy)
|
L4 Notes
|
|
Oct. 11
|
Exokernels
|
Engler & Kaashoek, Exterminate all operating system abstractions (proxy)
Engler et al., Exokernel: an operating system architecture for application-level resource management (proxy)
|
Exokernels Notes
|
|
Oct. 16
|
Midterm summary discussion
Project discussion
|
|
Midterm Study Guide
|
|
Oct. 18
|
Midterm Exam (LaTeX)
Proposals Due
|
|
|
|
Oct. 23
|
Old Code
|
Ozment & Schechter, Milk or Wine: Does Software Security Improve with Age?
|
|
|
Oct. 25
|
Old APIs
|
Bright, An in-depth look at WinRT
|
|
|
Oct. 30
|
|
|
|
|
Nov. 1
|
|
|
|
|
Nov. 6
|
|
|
|
|
Nov. 8
|
|
|
|
|
Nov. 13
|
|
|
|
|
Nov. 15
|
|
|
|
|
Nov. 20
|
|
|
|
|
Nov. 22
|
|
|
|
|
Nov. 27
|
|
|
|
|
Nov. 29
|
|
|
|
|
TBA
|
Final Exam
|
|
|