Computer Systems Security (Winter 2016) - Revision history

Keybra: /* Lectures and Exams */

2016-04-19T00:17:21Z

Lectures and Exams

← Older revision		Revision as of 00:17, 19 April 2016
Line 204:		Line 204:
	</td>		</td>
	<td>		<td>
	<p>[[SystemsSec 2016W Lecture 16\|~~Lecture 16~~]]		<p>[[SystemsSec 2016W Lecture 16\|Network Firewalls]]
	</p>		</p>
	</td>		</td>

2016-04-16T17:07:46Z

Lectures and Exams

← Older revision		Revision as of 17:07, 16 April 2016
Line 295:		Line 295:
	</td>		</td>
	<td>		<td>
	<p>Last-Minute Study Session		<p>Last-Minute Study Session in LA B146
	</p>		</p>
	</td>		</td>

2016-04-07T14:30:29Z

Lectures and Exams

← Older revision		Revision as of 14:30, 7 April 2016
Line 285:		Line 285:
	</td>		</td>
	<td>		<td>
	<p>[[SystemsSec 2016W Lecture 24\|~~Lecture 24~~]]		<p>[[SystemsSec 2016W Lecture 24\|Final Exam Review]]
	</p>		</p>
	</td>		</td>

2016-04-05T22:09:30Z

Lectures and Exams

← Older revision		Revision as of 22:09, 5 April 2016
Line 275:		Line 275:
	</td>		</td>
	<td>		<td>
	<p>[[SystemsSec 2016W Lecture 23\|~~Lecture 23~~]]		<p>[[SystemsSec 2016W Lecture 23\|Boxify and Android Permissions]]
	</p>		</p>
	</td>		</td>

2016-04-05T18:17:14Z

Lectures and Exams

← Older revision		Revision as of 18:17, 5 April 2016
Line 265:		Line 265:
	</td>		</td>
	<td>		<td>
	<p>[[SystemsSec 2016W Lecture 22\|~~Lecture 22~~]]		<p>[[SystemsSec 2016W Lecture 22\|Cookie Integrity and XSSI]]
	</p>		</p>
	</td>		</td>

2016-04-04T15:18:11Z

Lectures and Exams

@@ Line 286: / Line 286: @@
        <td>
        <p>[[SystemsSec 2016W Lecture 24|Lecture 24]]
        </p>
        </td>

2016-03-27T05:53:26Z

← Older revision		Revision as of 05:53, 27 March 2016
Line 245:		Line 245:
	</td>		</td>
	<td>		<td>
	<p>[[SystemsSec 2016W Lecture 20\|~~Lecture 20~~]]		<p>[[SystemsSec 2016W Lecture 20\|DDoS and Pinning]]
	</p>		</p>
	</td>		</td>

2016-03-24T21:29:12Z

Security Reading Analysis Guidelines: - fix really annoying typo

← Older revision		Revision as of 21:29, 24 March 2016
Line 339:		Line 339:
	For both kinds of papers, you should give your reaction by addressing questions like the following:		For both kinds of papers, you should give your reaction by addressing questions like the following:
	* Did you like the paper?		* Did you like the paper?
	* ~~What~~ it easy to understand, or was it hard to read?		* Was it easy to understand, or was it hard to read?
	* Did you learn much from the paper?		* Did you learn much from the paper?
	* How surprised were you by the result?		* How surprised were you by the result?

2016-03-16T16:00:02Z

Security Reading Analysis Guidelines

← Older revision		Revision as of 16:00, 16 March 2016
Line 346:		Line 346:

	Each analysis will be graded out of 10 as follows:		Each analysis will be graded out of 10 as follows:
	* 3 for demonstrating understanding of the content (preferably without summarizing)		* U: 3 for demonstrating understanding of the content (preferably without summarizing)
	* 3 for technical analysis (does it work)		* T: 3 for technical analysis (does it work)
	* 3 for contextual analysis (does it matter)		* C: 3 for contextual analysis (does it matter)
	* 1 for your viewpoint		* V: 1 for your viewpoint

2016-03-16T15:53:59Z

@@ Line 299: / Line 299: @@
        </td>
      <td><p></p></td></tr>
 </table>
@@ Line 396: / Line 344: @@
 Your analysis should not cover the above questions separately (this would tend to make for a very wordy analysis); instead, use these questions as a guide in writing a short essay (1-2 pages) on the paper in question.