<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://homeostasis.scs.carleton.ca/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Jessjohnson</id>
	<title>Soma-notes - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://homeostasis.scs.carleton.ca/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Jessjohnson"/>
	<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php/Special:Contributions/Jessjohnson"/>
	<updated>2026-05-14T01:21:32Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.42.1</generator>
	<entry>
		<id>https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20703</id>
		<title>SystemsSec 2016W Lecture 4</title>
		<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20703"/>
		<updated>2016-02-11T15:55:19Z</updated>

		<summary type="html">&lt;p&gt;Jessjohnson: /* Topics &amp;amp; Readings */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Topics &amp;amp; Readings===&lt;br /&gt;
----&lt;br /&gt;
* chroot jails&lt;br /&gt;
* MULTICS&lt;br /&gt;
* Trent Jaeger&#039;s &#039;&#039;Operating Systems Security&#039;&#039; textbook&lt;br /&gt;
* TCP IP Illustrated&lt;br /&gt;
&lt;br /&gt;
===Class Notes===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
A chroot jail isolates a single process from the rest of the system, and should be used by non-root users.&lt;br /&gt;
* BSD mechanism, not really a Linux thing&lt;br /&gt;
* limiting hierarchy to make a non-root dir seem like the root dir, forces hierarchy to be duplicated so that nothing seems weird&lt;br /&gt;
* fake root user gets ‘jailed’ into subset of hierarchy, and doesn’t really have real root privileges&lt;br /&gt;
* process has a different root dir in kernel, but to the fake root user it still seems like the root dir&lt;br /&gt;
* one kernel space, multiple user spaces&lt;br /&gt;
* kind of like OS virtualization&lt;br /&gt;
&lt;br /&gt;
=====DD-WRT=====&lt;br /&gt;
DD-WRT is firmware for routers. LinkSys used to make a router models that came with a Linux kernel on them, [https://en.wikipedia.org/wiki/Linksys_WRT54G_series#Hardware_and_revisions the WRT54G series].&lt;br /&gt;
&lt;br /&gt;
====Proxy vs VPN tunneling====&lt;br /&gt;
* proxies are for HTTP specifically&lt;br /&gt;
* VPN is for any internet traffic&lt;br /&gt;
If you&#039;re having a hard time understanding networking, [https://en.wikipedia.org/wiki/TCP/IP_Illustrated &#039;&#039;TCP IP illustrated&#039;&#039;] , look into reading these 3 volumes. They are highly recommended by Anil.&lt;br /&gt;
&lt;br /&gt;
====(Complex Security) Policies====&lt;br /&gt;
&#039;&#039;&amp;quot;Suck, don’t make them.&amp;quot;&#039;&#039; - Anil, 2016.&lt;br /&gt;
We can’t approximate how humans approach information with logic systems, so we shouldn&#039;t try.&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
&#039;&#039;&#039;Mult&#039;&#039;&#039;iplexed &#039;&#039;&#039;I&#039;&#039;&#039;nformation and &#039;&#039;&#039;C&#039;&#039;&#039;omputing &#039;&#039;&#039;S&#039;&#039;&#039;ervice&lt;br /&gt;
* supposed to be a “grown up” OS&lt;br /&gt;
* first OS to take security seriously&lt;br /&gt;
* took a &amp;quot;shotgun approach&amp;quot; to security, too much generality&lt;br /&gt;
* implemented a ring system which was overly complicated&lt;br /&gt;
&lt;br /&gt;
====UNIX====&lt;br /&gt;
Our favourite open sourced OS. All praise to the GNU.&lt;br /&gt;
* simplest security mechanisms, most usable&lt;br /&gt;
&lt;br /&gt;
====SELinux====&lt;br /&gt;
&#039;&#039;&#039;S&#039;&#039;&#039;ecurity &#039;&#039;&#039;E&#039;&#039;&#039;nhanced Linux&lt;br /&gt;
&lt;br /&gt;
A set of kernel modifications whose goals are to make the Linux kernel more secure. These mainly include implementing and enforcing security policies.&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* software that mediates all security decisions&lt;br /&gt;
* MULTICS designed to have a reference monitor, which was their ring system&lt;br /&gt;
* UNIX doesn’t really have one, processes (kind of) moderate security decisions together&lt;br /&gt;
&lt;br /&gt;
===Important Questions===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
* What is an OS jail?&lt;br /&gt;
* What would happen if a user broke out of a jail?&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What was good/bad about MULTICS?&lt;br /&gt;
* How did MULTICS affect UNIX?&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What is it&#039;s role in an OS?&lt;br /&gt;
* How is it implemented in UNIX and MULTICS?&lt;/div&gt;</summary>
		<author><name>Jessjohnson</name></author>
	</entry>
	<entry>
		<id>https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20696</id>
		<title>SystemsSec 2016W Lecture 4</title>
		<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20696"/>
		<updated>2016-02-09T21:07:09Z</updated>

		<summary type="html">&lt;p&gt;Jessjohnson: /* Topics &amp;amp; Readings */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Topics &amp;amp; Readings===&lt;br /&gt;
----&lt;br /&gt;
* chroot jails&lt;br /&gt;
* MULTICS&lt;br /&gt;
* Trent Jaeger&#039;s &#039;&#039;Operating Systems Security&#039;&#039; textbook&lt;br /&gt;
&lt;br /&gt;
===Class Notes===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
A chroot jail isolates a single process from the rest of the system, and should be used by non-root users.&lt;br /&gt;
* BSD mechanism, not really a Linux thing&lt;br /&gt;
* limiting hierarchy to make a non-root dir seem like the root dir, forces hierarchy to be duplicated so that nothing seems weird&lt;br /&gt;
* fake root user gets ‘jailed’ into subset of hierarchy, and doesn’t really have real root privileges&lt;br /&gt;
* process has a different root dir in kernel, but to the fake root user it still seems like the root dir&lt;br /&gt;
* one kernel space, multiple user spaces&lt;br /&gt;
* kind of like OS virtualization&lt;br /&gt;
&lt;br /&gt;
=====DD-WRT=====&lt;br /&gt;
DD-WRT is firmware for routers. LinkSys used to make a router models that came with a Linux kernel on them, [https://en.wikipedia.org/wiki/Linksys_WRT54G_series#Hardware_and_revisions the WRT54G series].&lt;br /&gt;
&lt;br /&gt;
====Proxy vs VPN tunneling====&lt;br /&gt;
* proxies are for HTTP specifically&lt;br /&gt;
* VPN is for any internet traffic&lt;br /&gt;
If you&#039;re having a hard time understanding networking, [https://en.wikipedia.org/wiki/TCP/IP_Illustrated &#039;&#039;TCP IP illustrated&#039;&#039;] , look into reading these 3 volumes. They are highly recommended by Anil.&lt;br /&gt;
&lt;br /&gt;
====(Complex Security) Policies====&lt;br /&gt;
&#039;&#039;&amp;quot;Suck, don’t make them.&amp;quot;&#039;&#039; - Anil, 2016.&lt;br /&gt;
We can’t approximate how humans approach information with logic systems, so we shouldn&#039;t try.&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
&#039;&#039;&#039;Mult&#039;&#039;&#039;iplexed &#039;&#039;&#039;I&#039;&#039;&#039;nformation and &#039;&#039;&#039;C&#039;&#039;&#039;omputing &#039;&#039;&#039;S&#039;&#039;&#039;ervice&lt;br /&gt;
* supposed to be a “grown up” OS&lt;br /&gt;
* first OS to take security seriously&lt;br /&gt;
* took a &amp;quot;shotgun approach&amp;quot; to security, too much generality&lt;br /&gt;
* implemented a ring system which was overly complicated&lt;br /&gt;
&lt;br /&gt;
====UNIX====&lt;br /&gt;
Our favourite open sourced OS. All praise to the GNU.&lt;br /&gt;
* simplest security mechanisms, most usable&lt;br /&gt;
&lt;br /&gt;
====SELinux====&lt;br /&gt;
&#039;&#039;&#039;S&#039;&#039;&#039;ecurity &#039;&#039;&#039;E&#039;&#039;&#039;nhanced Linux&lt;br /&gt;
&lt;br /&gt;
A set of kernel modifications whose goals are to make the Linux kernel more secure. These mainly include implementing and enforcing security policies.&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* software that mediates all security decisions&lt;br /&gt;
* MULTICS designed to have a reference monitor, which was their ring system&lt;br /&gt;
* UNIX doesn’t really have one, processes (kind of) moderate security decisions together&lt;br /&gt;
&lt;br /&gt;
===Important Questions===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
* What is an OS jail?&lt;br /&gt;
* What would happen if a user broke out of a jail?&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What was good/bad about MULTICS?&lt;br /&gt;
* How did MULTICS affect UNIX?&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What is it&#039;s role in an OS?&lt;br /&gt;
* How is it implemented in UNIX and MULTICS?&lt;/div&gt;</summary>
		<author><name>Jessjohnson</name></author>
	</entry>
	<entry>
		<id>https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20695</id>
		<title>SystemsSec 2016W Lecture 4</title>
		<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20695"/>
		<updated>2016-02-09T21:06:57Z</updated>

		<summary type="html">&lt;p&gt;Jessjohnson: /* Topics &amp;amp; Readings */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Topics &amp;amp; Readings===&lt;br /&gt;
----&lt;br /&gt;
* chroot jails&lt;br /&gt;
* MULTICS&lt;br /&gt;
* Trent Jaeger&#039;s &#039;&#039;Operating Systems Security&#039;&#039; Textbook&lt;br /&gt;
&lt;br /&gt;
===Class Notes===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
A chroot jail isolates a single process from the rest of the system, and should be used by non-root users.&lt;br /&gt;
* BSD mechanism, not really a Linux thing&lt;br /&gt;
* limiting hierarchy to make a non-root dir seem like the root dir, forces hierarchy to be duplicated so that nothing seems weird&lt;br /&gt;
* fake root user gets ‘jailed’ into subset of hierarchy, and doesn’t really have real root privileges&lt;br /&gt;
* process has a different root dir in kernel, but to the fake root user it still seems like the root dir&lt;br /&gt;
* one kernel space, multiple user spaces&lt;br /&gt;
* kind of like OS virtualization&lt;br /&gt;
&lt;br /&gt;
=====DD-WRT=====&lt;br /&gt;
DD-WRT is firmware for routers. LinkSys used to make a router models that came with a Linux kernel on them, [https://en.wikipedia.org/wiki/Linksys_WRT54G_series#Hardware_and_revisions the WRT54G series].&lt;br /&gt;
&lt;br /&gt;
====Proxy vs VPN tunneling====&lt;br /&gt;
* proxies are for HTTP specifically&lt;br /&gt;
* VPN is for any internet traffic&lt;br /&gt;
If you&#039;re having a hard time understanding networking, [https://en.wikipedia.org/wiki/TCP/IP_Illustrated &#039;&#039;TCP IP illustrated&#039;&#039;] , look into reading these 3 volumes. They are highly recommended by Anil.&lt;br /&gt;
&lt;br /&gt;
====(Complex Security) Policies====&lt;br /&gt;
&#039;&#039;&amp;quot;Suck, don’t make them.&amp;quot;&#039;&#039; - Anil, 2016.&lt;br /&gt;
We can’t approximate how humans approach information with logic systems, so we shouldn&#039;t try.&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
&#039;&#039;&#039;Mult&#039;&#039;&#039;iplexed &#039;&#039;&#039;I&#039;&#039;&#039;nformation and &#039;&#039;&#039;C&#039;&#039;&#039;omputing &#039;&#039;&#039;S&#039;&#039;&#039;ervice&lt;br /&gt;
* supposed to be a “grown up” OS&lt;br /&gt;
* first OS to take security seriously&lt;br /&gt;
* took a &amp;quot;shotgun approach&amp;quot; to security, too much generality&lt;br /&gt;
* implemented a ring system which was overly complicated&lt;br /&gt;
&lt;br /&gt;
====UNIX====&lt;br /&gt;
Our favourite open sourced OS. All praise to the GNU.&lt;br /&gt;
* simplest security mechanisms, most usable&lt;br /&gt;
&lt;br /&gt;
====SELinux====&lt;br /&gt;
&#039;&#039;&#039;S&#039;&#039;&#039;ecurity &#039;&#039;&#039;E&#039;&#039;&#039;nhanced Linux&lt;br /&gt;
&lt;br /&gt;
A set of kernel modifications whose goals are to make the Linux kernel more secure. These mainly include implementing and enforcing security policies.&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* software that mediates all security decisions&lt;br /&gt;
* MULTICS designed to have a reference monitor, which was their ring system&lt;br /&gt;
* UNIX doesn’t really have one, processes (kind of) moderate security decisions together&lt;br /&gt;
&lt;br /&gt;
===Important Questions===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
* What is an OS jail?&lt;br /&gt;
* What would happen if a user broke out of a jail?&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What was good/bad about MULTICS?&lt;br /&gt;
* How did MULTICS affect UNIX?&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What is it&#039;s role in an OS?&lt;br /&gt;
* How is it implemented in UNIX and MULTICS?&lt;/div&gt;</summary>
		<author><name>Jessjohnson</name></author>
	</entry>
	<entry>
		<id>https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20686</id>
		<title>SystemsSec 2016W Lecture 4</title>
		<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20686"/>
		<updated>2016-02-05T00:40:21Z</updated>

		<summary type="html">&lt;p&gt;Jessjohnson: /* UNIX */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Topics &amp;amp; Readings===&lt;br /&gt;
----&lt;br /&gt;
* chroot jails&lt;br /&gt;
* MULTICS&lt;br /&gt;
&lt;br /&gt;
===Class Notes===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
A chroot jail isolates a single process from the rest of the system, and should be used by non-root users.&lt;br /&gt;
* BSD mechanism, not really a Linux thing&lt;br /&gt;
* limiting hierarchy to make a non-root dir seem like the root dir, forces hierarchy to be duplicated so that nothing seems weird&lt;br /&gt;
* fake root user gets ‘jailed’ into subset of hierarchy, and doesn’t really have real root privileges&lt;br /&gt;
* process has a different root dir in kernel, but to the fake root user it still seems like the root dir&lt;br /&gt;
* one kernel space, multiple user spaces&lt;br /&gt;
* kind of like OS virtualization&lt;br /&gt;
&lt;br /&gt;
=====DD-WRT=====&lt;br /&gt;
DD-WRT is firmware for routers. LinkSys used to make a router models that came with a Linux kernel on them, [https://en.wikipedia.org/wiki/Linksys_WRT54G_series#Hardware_and_revisions the WRT54G series].&lt;br /&gt;
&lt;br /&gt;
====Proxy vs VPN tunneling====&lt;br /&gt;
* proxies are for HTTP specifically&lt;br /&gt;
* VPN is for any internet traffic&lt;br /&gt;
If you&#039;re having a hard time understanding networking, [https://en.wikipedia.org/wiki/TCP/IP_Illustrated &#039;&#039;TCP IP illustrated&#039;&#039;] , look into reading these 3 volumes. They are highly recommended by Anil.&lt;br /&gt;
&lt;br /&gt;
====(Complex Security) Policies====&lt;br /&gt;
&#039;&#039;&amp;quot;Suck, don’t make them.&amp;quot;&#039;&#039; - Anil, 2016.&lt;br /&gt;
We can’t approximate how humans approach information with logic systems, so we shouldn&#039;t try.&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
&#039;&#039;&#039;Mult&#039;&#039;&#039;iplexed &#039;&#039;&#039;I&#039;&#039;&#039;nformation and &#039;&#039;&#039;C&#039;&#039;&#039;omputing &#039;&#039;&#039;S&#039;&#039;&#039;ervice&lt;br /&gt;
* supposed to be a “grown up” OS&lt;br /&gt;
* first OS to take security seriously&lt;br /&gt;
* took a &amp;quot;shotgun approach&amp;quot; to security, too much generality&lt;br /&gt;
* implemented a ring system which was overly complicated&lt;br /&gt;
&lt;br /&gt;
====UNIX====&lt;br /&gt;
Our favourite open sourced OS. All praise to the GNU.&lt;br /&gt;
* simplest security mechanisms, most usable&lt;br /&gt;
&lt;br /&gt;
====SELinux====&lt;br /&gt;
&#039;&#039;&#039;S&#039;&#039;&#039;ecurity &#039;&#039;&#039;E&#039;&#039;&#039;nhanced Linux&lt;br /&gt;
&lt;br /&gt;
A set of kernel modifications whose goals are to make the Linux kernel more secure. These mainly include implementing and enforcing security policies.&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* software that mediates all security decisions&lt;br /&gt;
* MULTICS designed to have a reference monitor, which was their ring system&lt;br /&gt;
* UNIX doesn’t really have one, processes (kind of) moderate security decisions together&lt;br /&gt;
&lt;br /&gt;
===Important Questions===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
* What is an OS jail?&lt;br /&gt;
* What would happen if a user broke out of a jail?&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What was good/bad about MULTICS?&lt;br /&gt;
* How did MULTICS affect UNIX?&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What is it&#039;s role in an OS?&lt;br /&gt;
* How is it implemented in UNIX and MULTICS?&lt;/div&gt;</summary>
		<author><name>Jessjohnson</name></author>
	</entry>
	<entry>
		<id>https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20685</id>
		<title>SystemsSec 2016W Lecture 4</title>
		<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20685"/>
		<updated>2016-02-05T00:39:43Z</updated>

		<summary type="html">&lt;p&gt;Jessjohnson: /* MULTICS */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Topics &amp;amp; Readings===&lt;br /&gt;
----&lt;br /&gt;
* chroot jails&lt;br /&gt;
* MULTICS&lt;br /&gt;
&lt;br /&gt;
===Class Notes===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
A chroot jail isolates a single process from the rest of the system, and should be used by non-root users.&lt;br /&gt;
* BSD mechanism, not really a Linux thing&lt;br /&gt;
* limiting hierarchy to make a non-root dir seem like the root dir, forces hierarchy to be duplicated so that nothing seems weird&lt;br /&gt;
* fake root user gets ‘jailed’ into subset of hierarchy, and doesn’t really have real root privileges&lt;br /&gt;
* process has a different root dir in kernel, but to the fake root user it still seems like the root dir&lt;br /&gt;
* one kernel space, multiple user spaces&lt;br /&gt;
* kind of like OS virtualization&lt;br /&gt;
&lt;br /&gt;
=====DD-WRT=====&lt;br /&gt;
DD-WRT is firmware for routers. LinkSys used to make a router models that came with a Linux kernel on them, [https://en.wikipedia.org/wiki/Linksys_WRT54G_series#Hardware_and_revisions the WRT54G series].&lt;br /&gt;
&lt;br /&gt;
====Proxy vs VPN tunneling====&lt;br /&gt;
* proxies are for HTTP specifically&lt;br /&gt;
* VPN is for any internet traffic&lt;br /&gt;
If you&#039;re having a hard time understanding networking, [https://en.wikipedia.org/wiki/TCP/IP_Illustrated &#039;&#039;TCP IP illustrated&#039;&#039;] , look into reading these 3 volumes. They are highly recommended by Anil.&lt;br /&gt;
&lt;br /&gt;
====(Complex Security) Policies====&lt;br /&gt;
&#039;&#039;&amp;quot;Suck, don’t make them.&amp;quot;&#039;&#039; - Anil, 2016.&lt;br /&gt;
We can’t approximate how humans approach information with logic systems, so we shouldn&#039;t try.&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
&#039;&#039;&#039;Mult&#039;&#039;&#039;iplexed &#039;&#039;&#039;I&#039;&#039;&#039;nformation and &#039;&#039;&#039;C&#039;&#039;&#039;omputing &#039;&#039;&#039;S&#039;&#039;&#039;ervice&lt;br /&gt;
* supposed to be a “grown up” OS&lt;br /&gt;
* first OS to take security seriously&lt;br /&gt;
* took a &amp;quot;shotgun approach&amp;quot; to security, too much generality&lt;br /&gt;
* implemented a ring system which was overly complicated&lt;br /&gt;
&lt;br /&gt;
====UNIX====&lt;br /&gt;
Our favourite open sourced OS. All praise to the GNU.&lt;br /&gt;
* simplest mechanisms, most usable&lt;br /&gt;
&lt;br /&gt;
====SELinux====&lt;br /&gt;
&#039;&#039;&#039;S&#039;&#039;&#039;ecurity &#039;&#039;&#039;E&#039;&#039;&#039;nhanced Linux&lt;br /&gt;
&lt;br /&gt;
A set of kernel modifications whose goals are to make the Linux kernel more secure. These mainly include implementing and enforcing security policies.&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* software that mediates all security decisions&lt;br /&gt;
* MULTICS designed to have a reference monitor, which was their ring system&lt;br /&gt;
* UNIX doesn’t really have one, processes (kind of) moderate security decisions together&lt;br /&gt;
&lt;br /&gt;
===Important Questions===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
* What is an OS jail?&lt;br /&gt;
* What would happen if a user broke out of a jail?&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What was good/bad about MULTICS?&lt;br /&gt;
* How did MULTICS affect UNIX?&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What is it&#039;s role in an OS?&lt;br /&gt;
* How is it implemented in UNIX and MULTICS?&lt;/div&gt;</summary>
		<author><name>Jessjohnson</name></author>
	</entry>
	<entry>
		<id>https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20684</id>
		<title>SystemsSec 2016W Lecture 4</title>
		<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20684"/>
		<updated>2016-02-05T00:39:29Z</updated>

		<summary type="html">&lt;p&gt;Jessjohnson: /* MULTICS */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Topics &amp;amp; Readings===&lt;br /&gt;
----&lt;br /&gt;
* chroot jails&lt;br /&gt;
* MULTICS&lt;br /&gt;
&lt;br /&gt;
===Class Notes===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
A chroot jail isolates a single process from the rest of the system, and should be used by non-root users.&lt;br /&gt;
* BSD mechanism, not really a Linux thing&lt;br /&gt;
* limiting hierarchy to make a non-root dir seem like the root dir, forces hierarchy to be duplicated so that nothing seems weird&lt;br /&gt;
* fake root user gets ‘jailed’ into subset of hierarchy, and doesn’t really have real root privileges&lt;br /&gt;
* process has a different root dir in kernel, but to the fake root user it still seems like the root dir&lt;br /&gt;
* one kernel space, multiple user spaces&lt;br /&gt;
* kind of like OS virtualization&lt;br /&gt;
&lt;br /&gt;
=====DD-WRT=====&lt;br /&gt;
DD-WRT is firmware for routers. LinkSys used to make a router models that came with a Linux kernel on them, [https://en.wikipedia.org/wiki/Linksys_WRT54G_series#Hardware_and_revisions the WRT54G series].&lt;br /&gt;
&lt;br /&gt;
====Proxy vs VPN tunneling====&lt;br /&gt;
* proxies are for HTTP specifically&lt;br /&gt;
* VPN is for any internet traffic&lt;br /&gt;
If you&#039;re having a hard time understanding networking, [https://en.wikipedia.org/wiki/TCP/IP_Illustrated &#039;&#039;TCP IP illustrated&#039;&#039;] , look into reading these 3 volumes. They are highly recommended by Anil.&lt;br /&gt;
&lt;br /&gt;
====(Complex Security) Policies====&lt;br /&gt;
&#039;&#039;&amp;quot;Suck, don’t make them.&amp;quot;&#039;&#039; - Anil, 2016.&lt;br /&gt;
We can’t approximate how humans approach information with logic systems, so we shouldn&#039;t try.&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
&#039;&#039;&#039;Mul&#039;&#039;&#039;tiplexed &#039;&#039;&#039;I&#039;&#039;&#039;nformation and &#039;&#039;&#039;C&#039;&#039;&#039;omputing &#039;&#039;&#039;S&#039;&#039;&#039;ervice&lt;br /&gt;
* supposed to be a “grown up” OS&lt;br /&gt;
* first OS to take security seriously&lt;br /&gt;
* took a &amp;quot;shotgun approach&amp;quot; to security, too much generality&lt;br /&gt;
* implemented a ring system which was overly complicated&lt;br /&gt;
&lt;br /&gt;
====UNIX====&lt;br /&gt;
Our favourite open sourced OS. All praise to the GNU.&lt;br /&gt;
* simplest mechanisms, most usable&lt;br /&gt;
&lt;br /&gt;
====SELinux====&lt;br /&gt;
&#039;&#039;&#039;S&#039;&#039;&#039;ecurity &#039;&#039;&#039;E&#039;&#039;&#039;nhanced Linux&lt;br /&gt;
&lt;br /&gt;
A set of kernel modifications whose goals are to make the Linux kernel more secure. These mainly include implementing and enforcing security policies.&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* software that mediates all security decisions&lt;br /&gt;
* MULTICS designed to have a reference monitor, which was their ring system&lt;br /&gt;
* UNIX doesn’t really have one, processes (kind of) moderate security decisions together&lt;br /&gt;
&lt;br /&gt;
===Important Questions===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
* What is an OS jail?&lt;br /&gt;
* What would happen if a user broke out of a jail?&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What was good/bad about MULTICS?&lt;br /&gt;
* How did MULTICS affect UNIX?&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What is it&#039;s role in an OS?&lt;br /&gt;
* How is it implemented in UNIX and MULTICS?&lt;/div&gt;</summary>
		<author><name>Jessjohnson</name></author>
	</entry>
	<entry>
		<id>https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20683</id>
		<title>SystemsSec 2016W Lecture 4</title>
		<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20683"/>
		<updated>2016-02-05T00:38:50Z</updated>

		<summary type="html">&lt;p&gt;Jessjohnson: /* SELinux */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Topics &amp;amp; Readings===&lt;br /&gt;
----&lt;br /&gt;
* chroot jails&lt;br /&gt;
* MULTICS&lt;br /&gt;
&lt;br /&gt;
===Class Notes===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
A chroot jail isolates a single process from the rest of the system, and should be used by non-root users.&lt;br /&gt;
* BSD mechanism, not really a Linux thing&lt;br /&gt;
* limiting hierarchy to make a non-root dir seem like the root dir, forces hierarchy to be duplicated so that nothing seems weird&lt;br /&gt;
* fake root user gets ‘jailed’ into subset of hierarchy, and doesn’t really have real root privileges&lt;br /&gt;
* process has a different root dir in kernel, but to the fake root user it still seems like the root dir&lt;br /&gt;
* one kernel space, multiple user spaces&lt;br /&gt;
* kind of like OS virtualization&lt;br /&gt;
&lt;br /&gt;
=====DD-WRT=====&lt;br /&gt;
DD-WRT is firmware for routers. LinkSys used to make a router models that came with a Linux kernel on them, [https://en.wikipedia.org/wiki/Linksys_WRT54G_series#Hardware_and_revisions the WRT54G series].&lt;br /&gt;
&lt;br /&gt;
====Proxy vs VPN tunneling====&lt;br /&gt;
* proxies are for HTTP specifically&lt;br /&gt;
* VPN is for any internet traffic&lt;br /&gt;
If you&#039;re having a hard time understanding networking, [https://en.wikipedia.org/wiki/TCP/IP_Illustrated &#039;&#039;TCP IP illustrated&#039;&#039;] , look into reading these 3 volumes. They are highly recommended by Anil.&lt;br /&gt;
&lt;br /&gt;
====(Complex Security) Policies====&lt;br /&gt;
&#039;&#039;&amp;quot;Suck, don’t make them.&amp;quot;&#039;&#039; - Anil, 2016.&lt;br /&gt;
We can’t approximate how humans approach information with logic systems, so we shouldn&#039;t try.&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
Multiplexed Information and Computing Service&lt;br /&gt;
* supposed to be a “grown up” OS&lt;br /&gt;
* first OS to take security seriously&lt;br /&gt;
* took a &amp;quot;shotgun approach&amp;quot; to security, too much generality&lt;br /&gt;
* implemented a ring system which was overly complicated&lt;br /&gt;
&lt;br /&gt;
====UNIX====&lt;br /&gt;
Our favourite open sourced OS. All praise to the GNU.&lt;br /&gt;
* simplest mechanisms, most usable&lt;br /&gt;
&lt;br /&gt;
====SELinux====&lt;br /&gt;
&#039;&#039;&#039;S&#039;&#039;&#039;ecurity &#039;&#039;&#039;E&#039;&#039;&#039;nhanced Linux&lt;br /&gt;
&lt;br /&gt;
A set of kernel modifications whose goals are to make the Linux kernel more secure. These mainly include implementing and enforcing security policies.&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* software that mediates all security decisions&lt;br /&gt;
* MULTICS designed to have a reference monitor, which was their ring system&lt;br /&gt;
* UNIX doesn’t really have one, processes (kind of) moderate security decisions together&lt;br /&gt;
&lt;br /&gt;
===Important Questions===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
* What is an OS jail?&lt;br /&gt;
* What would happen if a user broke out of a jail?&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What was good/bad about MULTICS?&lt;br /&gt;
* How did MULTICS affect UNIX?&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What is it&#039;s role in an OS?&lt;br /&gt;
* How is it implemented in UNIX and MULTICS?&lt;/div&gt;</summary>
		<author><name>Jessjohnson</name></author>
	</entry>
	<entry>
		<id>https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20682</id>
		<title>SystemsSec 2016W Lecture 4</title>
		<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20682"/>
		<updated>2016-02-05T00:38:28Z</updated>

		<summary type="html">&lt;p&gt;Jessjohnson: /* (Complex Security) Policies */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Topics &amp;amp; Readings===&lt;br /&gt;
----&lt;br /&gt;
* chroot jails&lt;br /&gt;
* MULTICS&lt;br /&gt;
&lt;br /&gt;
===Class Notes===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
A chroot jail isolates a single process from the rest of the system, and should be used by non-root users.&lt;br /&gt;
* BSD mechanism, not really a Linux thing&lt;br /&gt;
* limiting hierarchy to make a non-root dir seem like the root dir, forces hierarchy to be duplicated so that nothing seems weird&lt;br /&gt;
* fake root user gets ‘jailed’ into subset of hierarchy, and doesn’t really have real root privileges&lt;br /&gt;
* process has a different root dir in kernel, but to the fake root user it still seems like the root dir&lt;br /&gt;
* one kernel space, multiple user spaces&lt;br /&gt;
* kind of like OS virtualization&lt;br /&gt;
&lt;br /&gt;
=====DD-WRT=====&lt;br /&gt;
DD-WRT is firmware for routers. LinkSys used to make a router models that came with a Linux kernel on them, [https://en.wikipedia.org/wiki/Linksys_WRT54G_series#Hardware_and_revisions the WRT54G series].&lt;br /&gt;
&lt;br /&gt;
====Proxy vs VPN tunneling====&lt;br /&gt;
* proxies are for HTTP specifically&lt;br /&gt;
* VPN is for any internet traffic&lt;br /&gt;
If you&#039;re having a hard time understanding networking, [https://en.wikipedia.org/wiki/TCP/IP_Illustrated &#039;&#039;TCP IP illustrated&#039;&#039;] , look into reading these 3 volumes. They are highly recommended by Anil.&lt;br /&gt;
&lt;br /&gt;
====(Complex Security) Policies====&lt;br /&gt;
&#039;&#039;&amp;quot;Suck, don’t make them.&amp;quot;&#039;&#039; - Anil, 2016.&lt;br /&gt;
We can’t approximate how humans approach information with logic systems, so we shouldn&#039;t try.&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
Multiplexed Information and Computing Service&lt;br /&gt;
* supposed to be a “grown up” OS&lt;br /&gt;
* first OS to take security seriously&lt;br /&gt;
* took a &amp;quot;shotgun approach&amp;quot; to security, too much generality&lt;br /&gt;
* implemented a ring system which was overly complicated&lt;br /&gt;
&lt;br /&gt;
====UNIX====&lt;br /&gt;
Our favourite open sourced OS. All praise to the GNU.&lt;br /&gt;
* simplest mechanisms, most usable&lt;br /&gt;
&lt;br /&gt;
====SELinux====&lt;br /&gt;
&#039;&#039;&#039;S&#039;&#039;&#039;ecurity &#039;&#039;&#039;E&#039;&#039;&#039;nhanced Linux&lt;br /&gt;
A set of kernel modifications whose goals are to make the Linux kernel more secure. These mainly include implementing and enforcing security policies.&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* software that mediates all security decisions&lt;br /&gt;
* MULTICS designed to have a reference monitor, which was their ring system&lt;br /&gt;
* UNIX doesn’t really have one, processes (kind of) moderate security decisions together&lt;br /&gt;
&lt;br /&gt;
===Important Questions===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
* What is an OS jail?&lt;br /&gt;
* What would happen if a user broke out of a jail?&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What was good/bad about MULTICS?&lt;br /&gt;
* How did MULTICS affect UNIX?&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What is it&#039;s role in an OS?&lt;br /&gt;
* How is it implemented in UNIX and MULTICS?&lt;/div&gt;</summary>
		<author><name>Jessjohnson</name></author>
	</entry>
	<entry>
		<id>https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20681</id>
		<title>SystemsSec 2016W Lecture 4</title>
		<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20681"/>
		<updated>2016-02-05T00:38:13Z</updated>

		<summary type="html">&lt;p&gt;Jessjohnson: /* (Complex Security) Policies */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Topics &amp;amp; Readings===&lt;br /&gt;
----&lt;br /&gt;
* chroot jails&lt;br /&gt;
* MULTICS&lt;br /&gt;
&lt;br /&gt;
===Class Notes===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
A chroot jail isolates a single process from the rest of the system, and should be used by non-root users.&lt;br /&gt;
* BSD mechanism, not really a Linux thing&lt;br /&gt;
* limiting hierarchy to make a non-root dir seem like the root dir, forces hierarchy to be duplicated so that nothing seems weird&lt;br /&gt;
* fake root user gets ‘jailed’ into subset of hierarchy, and doesn’t really have real root privileges&lt;br /&gt;
* process has a different root dir in kernel, but to the fake root user it still seems like the root dir&lt;br /&gt;
* one kernel space, multiple user spaces&lt;br /&gt;
* kind of like OS virtualization&lt;br /&gt;
&lt;br /&gt;
=====DD-WRT=====&lt;br /&gt;
DD-WRT is firmware for routers. LinkSys used to make a router models that came with a Linux kernel on them, [https://en.wikipedia.org/wiki/Linksys_WRT54G_series#Hardware_and_revisions the WRT54G series].&lt;br /&gt;
&lt;br /&gt;
====Proxy vs VPN tunneling====&lt;br /&gt;
* proxies are for HTTP specifically&lt;br /&gt;
* VPN is for any internet traffic&lt;br /&gt;
If you&#039;re having a hard time understanding networking, [https://en.wikipedia.org/wiki/TCP/IP_Illustrated &#039;&#039;TCP IP illustrated&#039;&#039;] , look into reading these 3 volumes. They are highly recommended by Anil.&lt;br /&gt;
&lt;br /&gt;
====(Complex Security) Policies====&lt;br /&gt;
&#039;&#039;&amp;quot;Suck, don’t make them.&amp;quot;&#039;&#039; - Anil, 2016.&lt;br /&gt;
We can’t approximate how humans approach information with logic systems, so we shouldn&#039;t try. If we could we would have solved the AI problem.&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
Multiplexed Information and Computing Service&lt;br /&gt;
* supposed to be a “grown up” OS&lt;br /&gt;
* first OS to take security seriously&lt;br /&gt;
* took a &amp;quot;shotgun approach&amp;quot; to security, too much generality&lt;br /&gt;
* implemented a ring system which was overly complicated&lt;br /&gt;
&lt;br /&gt;
====UNIX====&lt;br /&gt;
Our favourite open sourced OS. All praise to the GNU.&lt;br /&gt;
* simplest mechanisms, most usable&lt;br /&gt;
&lt;br /&gt;
====SELinux====&lt;br /&gt;
&#039;&#039;&#039;S&#039;&#039;&#039;ecurity &#039;&#039;&#039;E&#039;&#039;&#039;nhanced Linux&lt;br /&gt;
A set of kernel modifications whose goals are to make the Linux kernel more secure. These mainly include implementing and enforcing security policies.&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* software that mediates all security decisions&lt;br /&gt;
* MULTICS designed to have a reference monitor, which was their ring system&lt;br /&gt;
* UNIX doesn’t really have one, processes (kind of) moderate security decisions together&lt;br /&gt;
&lt;br /&gt;
===Important Questions===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
* What is an OS jail?&lt;br /&gt;
* What would happen if a user broke out of a jail?&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What was good/bad about MULTICS?&lt;br /&gt;
* How did MULTICS affect UNIX?&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What is it&#039;s role in an OS?&lt;br /&gt;
* How is it implemented in UNIX and MULTICS?&lt;/div&gt;</summary>
		<author><name>Jessjohnson</name></author>
	</entry>
	<entry>
		<id>https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20680</id>
		<title>SystemsSec 2016W Lecture 4</title>
		<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20680"/>
		<updated>2016-02-05T00:37:48Z</updated>

		<summary type="html">&lt;p&gt;Jessjohnson: /* Proxy vs VPN tunneling */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Topics &amp;amp; Readings===&lt;br /&gt;
----&lt;br /&gt;
* chroot jails&lt;br /&gt;
* MULTICS&lt;br /&gt;
&lt;br /&gt;
===Class Notes===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
A chroot jail isolates a single process from the rest of the system, and should be used by non-root users.&lt;br /&gt;
* BSD mechanism, not really a Linux thing&lt;br /&gt;
* limiting hierarchy to make a non-root dir seem like the root dir, forces hierarchy to be duplicated so that nothing seems weird&lt;br /&gt;
* fake root user gets ‘jailed’ into subset of hierarchy, and doesn’t really have real root privileges&lt;br /&gt;
* process has a different root dir in kernel, but to the fake root user it still seems like the root dir&lt;br /&gt;
* one kernel space, multiple user spaces&lt;br /&gt;
* kind of like OS virtualization&lt;br /&gt;
&lt;br /&gt;
=====DD-WRT=====&lt;br /&gt;
DD-WRT is firmware for routers. LinkSys used to make a router models that came with a Linux kernel on them, [https://en.wikipedia.org/wiki/Linksys_WRT54G_series#Hardware_and_revisions the WRT54G series].&lt;br /&gt;
&lt;br /&gt;
====Proxy vs VPN tunneling====&lt;br /&gt;
* proxies are for HTTP specifically&lt;br /&gt;
* VPN is for any internet traffic&lt;br /&gt;
If you&#039;re having a hard time understanding networking, [https://en.wikipedia.org/wiki/TCP/IP_Illustrated &#039;&#039;TCP IP illustrated&#039;&#039;] , look into reading these 3 volumes. They are highly recommended by Anil.&lt;br /&gt;
&lt;br /&gt;
====(Complex Security) Policies====&lt;br /&gt;
* &amp;quot;Suck, don’t make them.&amp;quot; - Anil, 2016.&lt;br /&gt;
We can’t approximate how humans approach information with logic systems, so we shouldn&#039;t try. If we could we would have solved the AI problem.&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
Multiplexed Information and Computing Service&lt;br /&gt;
* supposed to be a “grown up” OS&lt;br /&gt;
* first OS to take security seriously&lt;br /&gt;
* took a &amp;quot;shotgun approach&amp;quot; to security, too much generality&lt;br /&gt;
* implemented a ring system which was overly complicated&lt;br /&gt;
&lt;br /&gt;
====UNIX====&lt;br /&gt;
Our favourite open sourced OS. All praise to the GNU.&lt;br /&gt;
* simplest mechanisms, most usable&lt;br /&gt;
&lt;br /&gt;
====SELinux====&lt;br /&gt;
&#039;&#039;&#039;S&#039;&#039;&#039;ecurity &#039;&#039;&#039;E&#039;&#039;&#039;nhanced Linux&lt;br /&gt;
A set of kernel modifications whose goals are to make the Linux kernel more secure. These mainly include implementing and enforcing security policies.&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* software that mediates all security decisions&lt;br /&gt;
* MULTICS designed to have a reference monitor, which was their ring system&lt;br /&gt;
* UNIX doesn’t really have one, processes (kind of) moderate security decisions together&lt;br /&gt;
&lt;br /&gt;
===Important Questions===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
* What is an OS jail?&lt;br /&gt;
* What would happen if a user broke out of a jail?&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What was good/bad about MULTICS?&lt;br /&gt;
* How did MULTICS affect UNIX?&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What is it&#039;s role in an OS?&lt;br /&gt;
* How is it implemented in UNIX and MULTICS?&lt;/div&gt;</summary>
		<author><name>Jessjohnson</name></author>
	</entry>
	<entry>
		<id>https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20679</id>
		<title>SystemsSec 2016W Lecture 4</title>
		<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20679"/>
		<updated>2016-02-05T00:35:36Z</updated>

		<summary type="html">&lt;p&gt;Jessjohnson: /* Jails */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Topics &amp;amp; Readings===&lt;br /&gt;
----&lt;br /&gt;
* chroot jails&lt;br /&gt;
* MULTICS&lt;br /&gt;
&lt;br /&gt;
===Class Notes===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
A chroot jail isolates a single process from the rest of the system, and should be used by non-root users.&lt;br /&gt;
* BSD mechanism, not really a Linux thing&lt;br /&gt;
* limiting hierarchy to make a non-root dir seem like the root dir, forces hierarchy to be duplicated so that nothing seems weird&lt;br /&gt;
* fake root user gets ‘jailed’ into subset of hierarchy, and doesn’t really have real root privileges&lt;br /&gt;
* process has a different root dir in kernel, but to the fake root user it still seems like the root dir&lt;br /&gt;
* one kernel space, multiple user spaces&lt;br /&gt;
* kind of like OS virtualization&lt;br /&gt;
&lt;br /&gt;
=====DD-WRT=====&lt;br /&gt;
DD-WRT is firmware for routers. LinkSys used to make a router models that came with a Linux kernel on them, [https://en.wikipedia.org/wiki/Linksys_WRT54G_series#Hardware_and_revisions the WRT54G series].&lt;br /&gt;
&lt;br /&gt;
====Proxy vs VPN tunneling====&lt;br /&gt;
* proxies are for HTTP specifically&lt;br /&gt;
* VPN is for any internet traffic&lt;br /&gt;
* TCP IP illustrated, to better understand networking&lt;br /&gt;
&lt;br /&gt;
====(Complex Security) Policies====&lt;br /&gt;
* &amp;quot;Suck, don’t make them.&amp;quot; - Anil, 2016.&lt;br /&gt;
We can’t approximate how humans approach information with logic systems, so we shouldn&#039;t try. If we could we would have solved the AI problem.&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
Multiplexed Information and Computing Service&lt;br /&gt;
* supposed to be a “grown up” OS&lt;br /&gt;
* first OS to take security seriously&lt;br /&gt;
* took a &amp;quot;shotgun approach&amp;quot; to security, too much generality&lt;br /&gt;
* implemented a ring system which was overly complicated&lt;br /&gt;
&lt;br /&gt;
====UNIX====&lt;br /&gt;
Our favourite open sourced OS. All praise to the GNU.&lt;br /&gt;
* simplest mechanisms, most usable&lt;br /&gt;
&lt;br /&gt;
====SELinux====&lt;br /&gt;
&#039;&#039;&#039;S&#039;&#039;&#039;ecurity &#039;&#039;&#039;E&#039;&#039;&#039;nhanced Linux&lt;br /&gt;
A set of kernel modifications whose goals are to make the Linux kernel more secure. These mainly include implementing and enforcing security policies.&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* software that mediates all security decisions&lt;br /&gt;
* MULTICS designed to have a reference monitor, which was their ring system&lt;br /&gt;
* UNIX doesn’t really have one, processes (kind of) moderate security decisions together&lt;br /&gt;
&lt;br /&gt;
===Important Questions===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
* What is an OS jail?&lt;br /&gt;
* What would happen if a user broke out of a jail?&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What was good/bad about MULTICS?&lt;br /&gt;
* How did MULTICS affect UNIX?&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What is it&#039;s role in an OS?&lt;br /&gt;
* How is it implemented in UNIX and MULTICS?&lt;/div&gt;</summary>
		<author><name>Jessjohnson</name></author>
	</entry>
	<entry>
		<id>https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20678</id>
		<title>SystemsSec 2016W Lecture 4</title>
		<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20678"/>
		<updated>2016-02-05T00:34:00Z</updated>

		<summary type="html">&lt;p&gt;Jessjohnson: /* Reference Monitor */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Topics &amp;amp; Readings===&lt;br /&gt;
----&lt;br /&gt;
* chroot jails&lt;br /&gt;
* MULTICS&lt;br /&gt;
&lt;br /&gt;
===Class Notes===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
* better version of chmod&lt;br /&gt;
* BSD mechanism, not really a Linux thing&lt;br /&gt;
* limiting hierarchy to make a non-root dir seem like the root dir, forces hierarchy to be duplicated so that nothing seems weird&lt;br /&gt;
* fake root user gets ‘jailed’ into subset of hierarchy, and doesn’t really have real root privileges&lt;br /&gt;
* process has a different root dir in kernel, but to the fake root user it still seems like the root dir&lt;br /&gt;
* one kernel space, multiple user spaces&lt;br /&gt;
* kind of like OS virtualization&lt;br /&gt;
&lt;br /&gt;
=====DD-WRT=====&lt;br /&gt;
DD-WRT is firmware for routers. LinkSys used to make a router models that came with a Linux kernel on them, [https://en.wikipedia.org/wiki/Linksys_WRT54G_series#Hardware_and_revisions the WRT54G series].&lt;br /&gt;
&lt;br /&gt;
====Proxy vs VPN tunneling====&lt;br /&gt;
* proxies are for HTTP specifically&lt;br /&gt;
* VPN is for any internet traffic&lt;br /&gt;
* TCP IP illustrated, to better understand networking&lt;br /&gt;
&lt;br /&gt;
====(Complex Security) Policies====&lt;br /&gt;
* &amp;quot;Suck, don’t make them.&amp;quot; - Anil, 2016.&lt;br /&gt;
We can’t approximate how humans approach information with logic systems, so we shouldn&#039;t try. If we could we would have solved the AI problem.&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
Multiplexed Information and Computing Service&lt;br /&gt;
* supposed to be a “grown up” OS&lt;br /&gt;
* first OS to take security seriously&lt;br /&gt;
* took a &amp;quot;shotgun approach&amp;quot; to security, too much generality&lt;br /&gt;
* implemented a ring system which was overly complicated&lt;br /&gt;
&lt;br /&gt;
====UNIX====&lt;br /&gt;
Our favourite open sourced OS. All praise to the GNU.&lt;br /&gt;
* simplest mechanisms, most usable&lt;br /&gt;
&lt;br /&gt;
====SELinux====&lt;br /&gt;
&#039;&#039;&#039;S&#039;&#039;&#039;ecurity &#039;&#039;&#039;E&#039;&#039;&#039;nhanced Linux&lt;br /&gt;
A set of kernel modifications whose goals are to make the Linux kernel more secure. These mainly include implementing and enforcing security policies.&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* software that mediates all security decisions&lt;br /&gt;
* MULTICS designed to have a reference monitor, which was their ring system&lt;br /&gt;
* UNIX doesn’t really have one, processes (kind of) moderate security decisions together&lt;br /&gt;
&lt;br /&gt;
===Important Questions===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
* What is an OS jail?&lt;br /&gt;
* What would happen if a user broke out of a jail?&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What was good/bad about MULTICS?&lt;br /&gt;
* How did MULTICS affect UNIX?&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What is it&#039;s role in an OS?&lt;br /&gt;
* How is it implemented in UNIX and MULTICS?&lt;/div&gt;</summary>
		<author><name>Jessjohnson</name></author>
	</entry>
	<entry>
		<id>https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20677</id>
		<title>SystemsSec 2016W Lecture 4</title>
		<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20677"/>
		<updated>2016-02-05T00:30:37Z</updated>

		<summary type="html">&lt;p&gt;Jessjohnson: /* UNIX */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Topics &amp;amp; Readings===&lt;br /&gt;
----&lt;br /&gt;
* chroot jails&lt;br /&gt;
* MULTICS&lt;br /&gt;
&lt;br /&gt;
===Class Notes===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
* better version of chmod&lt;br /&gt;
* BSD mechanism, not really a Linux thing&lt;br /&gt;
* limiting hierarchy to make a non-root dir seem like the root dir, forces hierarchy to be duplicated so that nothing seems weird&lt;br /&gt;
* fake root user gets ‘jailed’ into subset of hierarchy, and doesn’t really have real root privileges&lt;br /&gt;
* process has a different root dir in kernel, but to the fake root user it still seems like the root dir&lt;br /&gt;
* one kernel space, multiple user spaces&lt;br /&gt;
* kind of like OS virtualization&lt;br /&gt;
&lt;br /&gt;
=====DD-WRT=====&lt;br /&gt;
DD-WRT is firmware for routers. LinkSys used to make a router models that came with a Linux kernel on them, [https://en.wikipedia.org/wiki/Linksys_WRT54G_series#Hardware_and_revisions the WRT54G series].&lt;br /&gt;
&lt;br /&gt;
====Proxy vs VPN tunneling====&lt;br /&gt;
* proxies are for HTTP specifically&lt;br /&gt;
* VPN is for any internet traffic&lt;br /&gt;
* TCP IP illustrated, to better understand networking&lt;br /&gt;
&lt;br /&gt;
====(Complex Security) Policies====&lt;br /&gt;
* &amp;quot;Suck, don’t make them.&amp;quot; - Anil, 2016.&lt;br /&gt;
We can’t approximate how humans approach information with logic systems, so we shouldn&#039;t try. If we could we would have solved the AI problem.&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
Multiplexed Information and Computing Service&lt;br /&gt;
* supposed to be a “grown up” OS&lt;br /&gt;
* first OS to take security seriously&lt;br /&gt;
* took a &amp;quot;shotgun approach&amp;quot; to security, too much generality&lt;br /&gt;
* implemented a ring system which was overly complicated&lt;br /&gt;
&lt;br /&gt;
====UNIX====&lt;br /&gt;
Our favourite open sourced OS. All praise to the GNU.&lt;br /&gt;
* simplest mechanisms, most usable&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* software that mediates all security decisions&lt;br /&gt;
* MULTICS designed to have a reference monitor, which was their ring system&lt;br /&gt;
* UNIX doesn’t really have one, processes (kind of) moderate security decisions together&lt;br /&gt;
&lt;br /&gt;
===Important Questions===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
* What is an OS jail?&lt;br /&gt;
* What would happen if a user broke out of a jail?&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What was good/bad about MULTICS?&lt;br /&gt;
* How did MULTICS affect UNIX?&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What is it&#039;s role in an OS?&lt;br /&gt;
* How is it implemented in UNIX and MULTICS?&lt;/div&gt;</summary>
		<author><name>Jessjohnson</name></author>
	</entry>
	<entry>
		<id>https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20676</id>
		<title>SystemsSec 2016W Lecture 4</title>
		<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20676"/>
		<updated>2016-02-05T00:29:20Z</updated>

		<summary type="html">&lt;p&gt;Jessjohnson: /* MULTICS */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Topics &amp;amp; Readings===&lt;br /&gt;
----&lt;br /&gt;
* chroot jails&lt;br /&gt;
* MULTICS&lt;br /&gt;
&lt;br /&gt;
===Class Notes===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
* better version of chmod&lt;br /&gt;
* BSD mechanism, not really a Linux thing&lt;br /&gt;
* limiting hierarchy to make a non-root dir seem like the root dir, forces hierarchy to be duplicated so that nothing seems weird&lt;br /&gt;
* fake root user gets ‘jailed’ into subset of hierarchy, and doesn’t really have real root privileges&lt;br /&gt;
* process has a different root dir in kernel, but to the fake root user it still seems like the root dir&lt;br /&gt;
* one kernel space, multiple user spaces&lt;br /&gt;
* kind of like OS virtualization&lt;br /&gt;
&lt;br /&gt;
=====DD-WRT=====&lt;br /&gt;
DD-WRT is firmware for routers. LinkSys used to make a router models that came with a Linux kernel on them, [https://en.wikipedia.org/wiki/Linksys_WRT54G_series#Hardware_and_revisions the WRT54G series].&lt;br /&gt;
&lt;br /&gt;
====Proxy vs VPN tunneling====&lt;br /&gt;
* proxies are for HTTP specifically&lt;br /&gt;
* VPN is for any internet traffic&lt;br /&gt;
* TCP IP illustrated, to better understand networking&lt;br /&gt;
&lt;br /&gt;
====(Complex Security) Policies====&lt;br /&gt;
* &amp;quot;Suck, don’t make them.&amp;quot; - Anil, 2016.&lt;br /&gt;
We can’t approximate how humans approach information with logic systems, so we shouldn&#039;t try. If we could we would have solved the AI problem.&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
Multiplexed Information and Computing Service&lt;br /&gt;
* supposed to be a “grown up” OS&lt;br /&gt;
* first OS to take security seriously&lt;br /&gt;
* took a &amp;quot;shotgun approach&amp;quot; to security, too much generality&lt;br /&gt;
* implemented a ring system which was overly complicated&lt;br /&gt;
&lt;br /&gt;
====UNIX====&lt;br /&gt;
* simplest mechanisms, most usable&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* software that mediates all security decisions&lt;br /&gt;
* MULTICS designed to have a reference monitor, which was their ring system&lt;br /&gt;
* UNIX doesn’t really have one, processes (kind of) moderate security decisions together&lt;br /&gt;
&lt;br /&gt;
===Important Questions===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
* What is an OS jail?&lt;br /&gt;
* What would happen if a user broke out of a jail?&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What was good/bad about MULTICS?&lt;br /&gt;
* How did MULTICS affect UNIX?&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What is it&#039;s role in an OS?&lt;br /&gt;
* How is it implemented in UNIX and MULTICS?&lt;/div&gt;</summary>
		<author><name>Jessjohnson</name></author>
	</entry>
	<entry>
		<id>https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20675</id>
		<title>SystemsSec 2016W Lecture 4</title>
		<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20675"/>
		<updated>2016-02-05T00:28:49Z</updated>

		<summary type="html">&lt;p&gt;Jessjohnson: /* (Complex Security) Policies */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Topics &amp;amp; Readings===&lt;br /&gt;
----&lt;br /&gt;
* chroot jails&lt;br /&gt;
* MULTICS&lt;br /&gt;
&lt;br /&gt;
===Class Notes===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
* better version of chmod&lt;br /&gt;
* BSD mechanism, not really a Linux thing&lt;br /&gt;
* limiting hierarchy to make a non-root dir seem like the root dir, forces hierarchy to be duplicated so that nothing seems weird&lt;br /&gt;
* fake root user gets ‘jailed’ into subset of hierarchy, and doesn’t really have real root privileges&lt;br /&gt;
* process has a different root dir in kernel, but to the fake root user it still seems like the root dir&lt;br /&gt;
* one kernel space, multiple user spaces&lt;br /&gt;
* kind of like OS virtualization&lt;br /&gt;
&lt;br /&gt;
=====DD-WRT=====&lt;br /&gt;
DD-WRT is firmware for routers. LinkSys used to make a router models that came with a Linux kernel on them, [https://en.wikipedia.org/wiki/Linksys_WRT54G_series#Hardware_and_revisions the WRT54G series].&lt;br /&gt;
&lt;br /&gt;
====Proxy vs VPN tunneling====&lt;br /&gt;
* proxies are for HTTP specifically&lt;br /&gt;
* VPN is for any internet traffic&lt;br /&gt;
* TCP IP illustrated, to better understand networking&lt;br /&gt;
&lt;br /&gt;
====(Complex Security) Policies====&lt;br /&gt;
* &amp;quot;Suck, don’t make them.&amp;quot; - Anil, 2016.&lt;br /&gt;
We can’t approximate how humans approach information with logic systems, so we shouldn&#039;t try. If we could we would have solved the AI problem.&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* supposed to be a “grown up” OS&lt;br /&gt;
* first OS to take security seriously&lt;br /&gt;
* took a &amp;quot;shotgun approach&amp;quot; to security, too much generality&lt;br /&gt;
* implemented a ring system which was overly complicated&lt;br /&gt;
&lt;br /&gt;
====UNIX====&lt;br /&gt;
* simplest mechanisms, most usable&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* software that mediates all security decisions&lt;br /&gt;
* MULTICS designed to have a reference monitor, which was their ring system&lt;br /&gt;
* UNIX doesn’t really have one, processes (kind of) moderate security decisions together&lt;br /&gt;
&lt;br /&gt;
===Important Questions===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
* What is an OS jail?&lt;br /&gt;
* What would happen if a user broke out of a jail?&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What was good/bad about MULTICS?&lt;br /&gt;
* How did MULTICS affect UNIX?&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What is it&#039;s role in an OS?&lt;br /&gt;
* How is it implemented in UNIX and MULTICS?&lt;/div&gt;</summary>
		<author><name>Jessjohnson</name></author>
	</entry>
	<entry>
		<id>https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20674</id>
		<title>SystemsSec 2016W Lecture 4</title>
		<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20674"/>
		<updated>2016-02-05T00:27:57Z</updated>

		<summary type="html">&lt;p&gt;Jessjohnson: /* Important Questions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Topics &amp;amp; Readings===&lt;br /&gt;
----&lt;br /&gt;
* chroot jails&lt;br /&gt;
* MULTICS&lt;br /&gt;
&lt;br /&gt;
===Class Notes===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
* better version of chmod&lt;br /&gt;
* BSD mechanism, not really a Linux thing&lt;br /&gt;
* limiting hierarchy to make a non-root dir seem like the root dir, forces hierarchy to be duplicated so that nothing seems weird&lt;br /&gt;
* fake root user gets ‘jailed’ into subset of hierarchy, and doesn’t really have real root privileges&lt;br /&gt;
* process has a different root dir in kernel, but to the fake root user it still seems like the root dir&lt;br /&gt;
* one kernel space, multiple user spaces&lt;br /&gt;
* kind of like OS virtualization&lt;br /&gt;
&lt;br /&gt;
=====DD-WRT=====&lt;br /&gt;
DD-WRT is firmware for routers. LinkSys used to make a router models that came with a Linux kernel on them, [https://en.wikipedia.org/wiki/Linksys_WRT54G_series#Hardware_and_revisions the WRT54G series].&lt;br /&gt;
&lt;br /&gt;
====Proxy vs VPN tunneling====&lt;br /&gt;
* proxies are for HTTP specifically&lt;br /&gt;
* VPN is for any internet traffic&lt;br /&gt;
* TCP IP illustrated, to better understand networking&lt;br /&gt;
&lt;br /&gt;
====(Complex Security) Policies====&lt;br /&gt;
* &amp;quot;Suck, don’t make them.&amp;quot; - Anil, 2016.&lt;br /&gt;
* can’t approximate how humans approach information with logic systems&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* supposed to be a “grown up” OS&lt;br /&gt;
* first OS to take security seriously&lt;br /&gt;
* took a &amp;quot;shotgun approach&amp;quot; to security, too much generality&lt;br /&gt;
* implemented a ring system which was overly complicated&lt;br /&gt;
&lt;br /&gt;
====UNIX====&lt;br /&gt;
* simplest mechanisms, most usable&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* software that mediates all security decisions&lt;br /&gt;
* MULTICS designed to have a reference monitor, which was their ring system&lt;br /&gt;
* UNIX doesn’t really have one, processes (kind of) moderate security decisions together&lt;br /&gt;
&lt;br /&gt;
===Important Questions===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
* What is an OS jail?&lt;br /&gt;
* What would happen if a user broke out of a jail?&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What was good/bad about MULTICS?&lt;br /&gt;
* How did MULTICS affect UNIX?&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What is it&#039;s role in an OS?&lt;br /&gt;
* How is it implemented in UNIX and MULTICS?&lt;/div&gt;</summary>
		<author><name>Jessjohnson</name></author>
	</entry>
	<entry>
		<id>https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20673</id>
		<title>SystemsSec 2016W Lecture 4</title>
		<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20673"/>
		<updated>2016-02-05T00:27:48Z</updated>

		<summary type="html">&lt;p&gt;Jessjohnson: /* Topics &amp;amp; Readings */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Topics &amp;amp; Readings===&lt;br /&gt;
----&lt;br /&gt;
* chroot jails&lt;br /&gt;
* MULTICS&lt;br /&gt;
&lt;br /&gt;
===Class Notes===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
* better version of chmod&lt;br /&gt;
* BSD mechanism, not really a Linux thing&lt;br /&gt;
* limiting hierarchy to make a non-root dir seem like the root dir, forces hierarchy to be duplicated so that nothing seems weird&lt;br /&gt;
* fake root user gets ‘jailed’ into subset of hierarchy, and doesn’t really have real root privileges&lt;br /&gt;
* process has a different root dir in kernel, but to the fake root user it still seems like the root dir&lt;br /&gt;
* one kernel space, multiple user spaces&lt;br /&gt;
* kind of like OS virtualization&lt;br /&gt;
&lt;br /&gt;
=====DD-WRT=====&lt;br /&gt;
DD-WRT is firmware for routers. LinkSys used to make a router models that came with a Linux kernel on them, [https://en.wikipedia.org/wiki/Linksys_WRT54G_series#Hardware_and_revisions the WRT54G series].&lt;br /&gt;
&lt;br /&gt;
====Proxy vs VPN tunneling====&lt;br /&gt;
* proxies are for HTTP specifically&lt;br /&gt;
* VPN is for any internet traffic&lt;br /&gt;
* TCP IP illustrated, to better understand networking&lt;br /&gt;
&lt;br /&gt;
====(Complex Security) Policies====&lt;br /&gt;
* &amp;quot;Suck, don’t make them.&amp;quot; - Anil, 2016.&lt;br /&gt;
* can’t approximate how humans approach information with logic systems&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* supposed to be a “grown up” OS&lt;br /&gt;
* first OS to take security seriously&lt;br /&gt;
* took a &amp;quot;shotgun approach&amp;quot; to security, too much generality&lt;br /&gt;
* implemented a ring system which was overly complicated&lt;br /&gt;
&lt;br /&gt;
====UNIX====&lt;br /&gt;
* simplest mechanisms, most usable&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* software that mediates all security decisions&lt;br /&gt;
* MULTICS designed to have a reference monitor, which was their ring system&lt;br /&gt;
* UNIX doesn’t really have one, processes (kind of) moderate security decisions together&lt;br /&gt;
&lt;br /&gt;
===Important Questions===&lt;br /&gt;
====Jails====&lt;br /&gt;
* What is an OS jail?&lt;br /&gt;
* What would happen if a user broke out of a jail?&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What was good/bad about MULTICS?&lt;br /&gt;
* How did MULTICS affect UNIX?&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What is it&#039;s role in an OS?&lt;br /&gt;
* How is it implemented in UNIX and MULTICS?&lt;/div&gt;</summary>
		<author><name>Jessjohnson</name></author>
	</entry>
	<entry>
		<id>https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20672</id>
		<title>SystemsSec 2016W Lecture 4</title>
		<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20672"/>
		<updated>2016-02-05T00:27:35Z</updated>

		<summary type="html">&lt;p&gt;Jessjohnson: /* Class Notes */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Topics &amp;amp; Readings===&lt;br /&gt;
* chroot jails&lt;br /&gt;
* MULTICS&lt;br /&gt;
&lt;br /&gt;
===Class Notes===&lt;br /&gt;
----&lt;br /&gt;
====Jails====&lt;br /&gt;
* better version of chmod&lt;br /&gt;
* BSD mechanism, not really a Linux thing&lt;br /&gt;
* limiting hierarchy to make a non-root dir seem like the root dir, forces hierarchy to be duplicated so that nothing seems weird&lt;br /&gt;
* fake root user gets ‘jailed’ into subset of hierarchy, and doesn’t really have real root privileges&lt;br /&gt;
* process has a different root dir in kernel, but to the fake root user it still seems like the root dir&lt;br /&gt;
* one kernel space, multiple user spaces&lt;br /&gt;
* kind of like OS virtualization&lt;br /&gt;
&lt;br /&gt;
=====DD-WRT=====&lt;br /&gt;
DD-WRT is firmware for routers. LinkSys used to make a router models that came with a Linux kernel on them, [https://en.wikipedia.org/wiki/Linksys_WRT54G_series#Hardware_and_revisions the WRT54G series].&lt;br /&gt;
&lt;br /&gt;
====Proxy vs VPN tunneling====&lt;br /&gt;
* proxies are for HTTP specifically&lt;br /&gt;
* VPN is for any internet traffic&lt;br /&gt;
* TCP IP illustrated, to better understand networking&lt;br /&gt;
&lt;br /&gt;
====(Complex Security) Policies====&lt;br /&gt;
* &amp;quot;Suck, don’t make them.&amp;quot; - Anil, 2016.&lt;br /&gt;
* can’t approximate how humans approach information with logic systems&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* supposed to be a “grown up” OS&lt;br /&gt;
* first OS to take security seriously&lt;br /&gt;
* took a &amp;quot;shotgun approach&amp;quot; to security, too much generality&lt;br /&gt;
* implemented a ring system which was overly complicated&lt;br /&gt;
&lt;br /&gt;
====UNIX====&lt;br /&gt;
* simplest mechanisms, most usable&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* software that mediates all security decisions&lt;br /&gt;
* MULTICS designed to have a reference monitor, which was their ring system&lt;br /&gt;
* UNIX doesn’t really have one, processes (kind of) moderate security decisions together&lt;br /&gt;
&lt;br /&gt;
===Important Questions===&lt;br /&gt;
====Jails====&lt;br /&gt;
* What is an OS jail?&lt;br /&gt;
* What would happen if a user broke out of a jail?&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What was good/bad about MULTICS?&lt;br /&gt;
* How did MULTICS affect UNIX?&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What is it&#039;s role in an OS?&lt;br /&gt;
* How is it implemented in UNIX and MULTICS?&lt;/div&gt;</summary>
		<author><name>Jessjohnson</name></author>
	</entry>
	<entry>
		<id>https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20671</id>
		<title>SystemsSec 2016W Lecture 4</title>
		<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20671"/>
		<updated>2016-02-05T00:26:47Z</updated>

		<summary type="html">&lt;p&gt;Jessjohnson: /* DD-WRT */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Topics &amp;amp; Readings===&lt;br /&gt;
* chroot jails&lt;br /&gt;
* MULTICS&lt;br /&gt;
&lt;br /&gt;
===Class Notes===&lt;br /&gt;
&lt;br /&gt;
====Jails====&lt;br /&gt;
* better version of chmod&lt;br /&gt;
* BSD mechanism, not really a Linux thing&lt;br /&gt;
* limiting hierarchy to make a non-root dir seem like the root dir, forces hierarchy to be duplicated so that nothing seems weird&lt;br /&gt;
* fake root user gets ‘jailed’ into subset of hierarchy, and doesn’t really have real root privileges&lt;br /&gt;
* process has a different root dir in kernel, but to the fake root user it still seems like the root dir&lt;br /&gt;
* one kernel space, multiple user spaces&lt;br /&gt;
* kind of like OS virtualization&lt;br /&gt;
&lt;br /&gt;
=====DD-WRT=====&lt;br /&gt;
DD-WRT is firmware for routers. LinkSys used to make a router models that came with a Linux kernel on them, [https://en.wikipedia.org/wiki/Linksys_WRT54G_series#Hardware_and_revisions the WRT54G series].&lt;br /&gt;
&lt;br /&gt;
====Proxy vs VPN tunneling====&lt;br /&gt;
* proxies are for HTTP specifically&lt;br /&gt;
* VPN is for any internet traffic&lt;br /&gt;
* TCP IP illustrated, to better understand networking&lt;br /&gt;
&lt;br /&gt;
====(Complex Security) Policies====&lt;br /&gt;
* &amp;quot;Suck, don’t make them.&amp;quot; - Anil, 2016.&lt;br /&gt;
* can’t approximate how humans approach information with logic systems&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* supposed to be a “grown up” OS&lt;br /&gt;
* first OS to take security seriously&lt;br /&gt;
* took a &amp;quot;shotgun approach&amp;quot; to security, too much generality&lt;br /&gt;
* implemented a ring system which was overly complicated&lt;br /&gt;
&lt;br /&gt;
====UNIX====&lt;br /&gt;
* simplest mechanisms, most usable&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* software that mediates all security decisions&lt;br /&gt;
* MULTICS designed to have a reference monitor, which was their ring system&lt;br /&gt;
* UNIX doesn’t really have one, processes (kind of) moderate security decisions together&lt;br /&gt;
&lt;br /&gt;
===Important Questions===&lt;br /&gt;
====Jails====&lt;br /&gt;
* What is an OS jail?&lt;br /&gt;
* What would happen if a user broke out of a jail?&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What was good/bad about MULTICS?&lt;br /&gt;
* How did MULTICS affect UNIX?&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What is it&#039;s role in an OS?&lt;br /&gt;
* How is it implemented in UNIX and MULTICS?&lt;/div&gt;</summary>
		<author><name>Jessjohnson</name></author>
	</entry>
	<entry>
		<id>https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20670</id>
		<title>SystemsSec 2016W Lecture 4</title>
		<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20670"/>
		<updated>2016-02-05T00:21:20Z</updated>

		<summary type="html">&lt;p&gt;Jessjohnson: /* Important Concepts */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Topics &amp;amp; Readings===&lt;br /&gt;
* chroot jails&lt;br /&gt;
* MULTICS&lt;br /&gt;
&lt;br /&gt;
===Class Notes===&lt;br /&gt;
&lt;br /&gt;
====Jails====&lt;br /&gt;
* better version of chmod&lt;br /&gt;
* BSD mechanism, not really a Linux thing&lt;br /&gt;
* limiting hierarchy to make a non-root dir seem like the root dir, forces hierarchy to be duplicated so that nothing seems weird&lt;br /&gt;
* fake root user gets ‘jailed’ into subset of hierarchy, and doesn’t really have real root privileges&lt;br /&gt;
* process has a different root dir in kernel, but to the fake root user it still seems like the root dir&lt;br /&gt;
* one kernel space, multiple user spaces&lt;br /&gt;
* kind of like OS virtualization&lt;br /&gt;
&lt;br /&gt;
====DD-WRT====&lt;br /&gt;
* firmware for routers&lt;br /&gt;
* WRT54G LinkSys router with a Linux kernel on it&lt;br /&gt;
&lt;br /&gt;
====Proxy vs VPN tunneling====&lt;br /&gt;
* proxies are for HTTP specifically&lt;br /&gt;
* VPN is for any internet traffic&lt;br /&gt;
* TCP IP illustrated, to better understand networking&lt;br /&gt;
&lt;br /&gt;
====(Complex Security) Policies====&lt;br /&gt;
* &amp;quot;Suck, don’t make them.&amp;quot; - Anil, 2016.&lt;br /&gt;
* can’t approximate how humans approach information with logic systems&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* supposed to be a “grown up” OS&lt;br /&gt;
* first OS to take security seriously&lt;br /&gt;
* took a &amp;quot;shotgun approach&amp;quot; to security, too much generality&lt;br /&gt;
* implemented a ring system which was overly complicated&lt;br /&gt;
&lt;br /&gt;
====UNIX====&lt;br /&gt;
* simplest mechanisms, most usable&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* software that mediates all security decisions&lt;br /&gt;
* MULTICS designed to have a reference monitor, which was their ring system&lt;br /&gt;
* UNIX doesn’t really have one, processes (kind of) moderate security decisions together&lt;br /&gt;
&lt;br /&gt;
===Important Questions===&lt;br /&gt;
====Jails====&lt;br /&gt;
* What is an OS jail?&lt;br /&gt;
* What would happen if a user broke out of a jail?&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What was good/bad about MULTICS?&lt;br /&gt;
* How did MULTICS affect UNIX?&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What is it&#039;s role in an OS?&lt;br /&gt;
* How is it implemented in UNIX and MULTICS?&lt;/div&gt;</summary>
		<author><name>Jessjohnson</name></author>
	</entry>
	<entry>
		<id>https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20667</id>
		<title>SystemsSec 2016W Lecture 4</title>
		<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20667"/>
		<updated>2016-02-04T15:16:38Z</updated>

		<summary type="html">&lt;p&gt;Jessjohnson: /* Reference Monitor */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Topics &amp;amp; Readings===&lt;br /&gt;
* chroot jails&lt;br /&gt;
* MULTICS&lt;br /&gt;
&lt;br /&gt;
===Class Notes===&lt;br /&gt;
&lt;br /&gt;
====Jails====&lt;br /&gt;
* better version of chmod&lt;br /&gt;
* BSD mechanism, not really a Linux thing&lt;br /&gt;
* limiting hierarchy to make a non-root dir seem like the root dir, forces hierarchy to be duplicated so that nothing seems weird&lt;br /&gt;
* fake root user gets ‘jailed’ into subset of hierarchy, and doesn’t really have real root privileges&lt;br /&gt;
* process has a different root dir in kernel, but to the fake root user it still seems like the root dir&lt;br /&gt;
* one kernel space, multiple user spaces&lt;br /&gt;
* kind of like OS virtualization&lt;br /&gt;
&lt;br /&gt;
====DD-WRT====&lt;br /&gt;
* firmware for routers&lt;br /&gt;
* WRT54G LinkSys router with a Linux kernel on it&lt;br /&gt;
&lt;br /&gt;
====Proxy vs VPN tunneling====&lt;br /&gt;
* proxies are for HTTP specifically&lt;br /&gt;
* VPN is for any internet traffic&lt;br /&gt;
* TCP IP illustrated, to better understand networking&lt;br /&gt;
&lt;br /&gt;
====(Complex Security) Policies====&lt;br /&gt;
* &amp;quot;Suck, don’t make them.&amp;quot; - Anil, 2016.&lt;br /&gt;
* can’t approximate how humans approach information with logic systems&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* supposed to be a “grown up” OS&lt;br /&gt;
* first OS to take security seriously&lt;br /&gt;
* took a &amp;quot;shotgun approach&amp;quot; to security, too much generality&lt;br /&gt;
* implemented a ring system which was overly complicated&lt;br /&gt;
&lt;br /&gt;
====UNIX====&lt;br /&gt;
* simplest mechanisms, most usable&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* software that mediates all security decisions&lt;br /&gt;
* MULTICS designed to have a reference monitor, which was their ring system&lt;br /&gt;
* UNIX doesn’t really have one, processes (kind of) moderate security decisions together&lt;br /&gt;
&lt;br /&gt;
===Important Concepts===&lt;br /&gt;
====Jails====&lt;br /&gt;
* What is an OS jail?&lt;br /&gt;
* What would happen if a user broke out of a jail?&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What was good/bad about MULTICS?&lt;br /&gt;
* How did MULTICS affect UNIX?&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What is it&#039;s role in an OS?&lt;br /&gt;
* How is it implemented in UNIX and MULTICS?&lt;/div&gt;</summary>
		<author><name>Jessjohnson</name></author>
	</entry>
	<entry>
		<id>https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20666</id>
		<title>SystemsSec 2016W Lecture 4</title>
		<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20666"/>
		<updated>2016-02-04T15:13:35Z</updated>

		<summary type="html">&lt;p&gt;Jessjohnson: /* Reference Monitor */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Topics &amp;amp; Readings===&lt;br /&gt;
* chroot jails&lt;br /&gt;
* MULTICS&lt;br /&gt;
&lt;br /&gt;
===Class Notes===&lt;br /&gt;
&lt;br /&gt;
====Jails====&lt;br /&gt;
* better version of chmod&lt;br /&gt;
* BSD mechanism, not really a Linux thing&lt;br /&gt;
* limiting hierarchy to make a non-root dir seem like the root dir, forces hierarchy to be duplicated so that nothing seems weird&lt;br /&gt;
* fake root user gets ‘jailed’ into subset of hierarchy, and doesn’t really have real root privileges&lt;br /&gt;
* process has a different root dir in kernel, but to the fake root user it still seems like the root dir&lt;br /&gt;
* one kernel space, multiple user spaces&lt;br /&gt;
* kind of like OS virtualization&lt;br /&gt;
&lt;br /&gt;
====DD-WRT====&lt;br /&gt;
* firmware for routers&lt;br /&gt;
* WRT54G LinkSys router with a Linux kernel on it&lt;br /&gt;
&lt;br /&gt;
====Proxy vs VPN tunneling====&lt;br /&gt;
* proxies are for HTTP specifically&lt;br /&gt;
* VPN is for any internet traffic&lt;br /&gt;
* TCP IP illustrated, to better understand networking&lt;br /&gt;
&lt;br /&gt;
====(Complex Security) Policies====&lt;br /&gt;
* &amp;quot;Suck, don’t make them.&amp;quot; - Anil, 2016.&lt;br /&gt;
* can’t approximate how humans approach information with logic systems&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* supposed to be a “grown up” OS&lt;br /&gt;
* first OS to take security seriously&lt;br /&gt;
* took a &amp;quot;shotgun approach&amp;quot; to security, too much generality&lt;br /&gt;
* implemented a ring system which was overly complicated&lt;br /&gt;
&lt;br /&gt;
====UNIX====&lt;br /&gt;
* simplest mechanisms, most usable&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* software that mediates all security decisions&lt;br /&gt;
* MULTICS designed to have a reference monitor, which was their ring system&lt;br /&gt;
* UNIX doesn’t really have one, processes (kind of) moderate security decisions together&lt;br /&gt;
&lt;br /&gt;
===Important Concepts===&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* What is it?&lt;br /&gt;
* What is it&#039;s role in an OS?&lt;br /&gt;
* How is it implemented in UNIX and MULTICS?&lt;/div&gt;</summary>
		<author><name>Jessjohnson</name></author>
	</entry>
	<entry>
		<id>https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20665</id>
		<title>SystemsSec 2016W Lecture 4</title>
		<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20665"/>
		<updated>2016-02-04T15:11:30Z</updated>

		<summary type="html">&lt;p&gt;Jessjohnson: /* Jails */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Topics &amp;amp; Readings===&lt;br /&gt;
* chroot jails&lt;br /&gt;
* MULTICS&lt;br /&gt;
&lt;br /&gt;
===Class Notes===&lt;br /&gt;
&lt;br /&gt;
====Jails====&lt;br /&gt;
* better version of chmod&lt;br /&gt;
* BSD mechanism, not really a Linux thing&lt;br /&gt;
* limiting hierarchy to make a non-root dir seem like the root dir, forces hierarchy to be duplicated so that nothing seems weird&lt;br /&gt;
* fake root user gets ‘jailed’ into subset of hierarchy, and doesn’t really have real root privileges&lt;br /&gt;
* process has a different root dir in kernel, but to the fake root user it still seems like the root dir&lt;br /&gt;
* one kernel space, multiple user spaces&lt;br /&gt;
* kind of like OS virtualization&lt;br /&gt;
&lt;br /&gt;
====DD-WRT====&lt;br /&gt;
* firmware for routers&lt;br /&gt;
* WRT54G LinkSys router with a Linux kernel on it&lt;br /&gt;
&lt;br /&gt;
====Proxy vs VPN tunneling====&lt;br /&gt;
* proxies are for HTTP specifically&lt;br /&gt;
* VPN is for any internet traffic&lt;br /&gt;
* TCP IP illustrated, to better understand networking&lt;br /&gt;
&lt;br /&gt;
====(Complex Security) Policies====&lt;br /&gt;
* &amp;quot;Suck, don’t make them.&amp;quot; - Anil, 2016.&lt;br /&gt;
* can’t approximate how humans approach information with logic systems&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* supposed to be a “grown up” OS&lt;br /&gt;
* first OS to take security seriously&lt;br /&gt;
* took a &amp;quot;shotgun approach&amp;quot; to security, too much generality&lt;br /&gt;
* implemented a ring system which was overly complicated&lt;br /&gt;
&lt;br /&gt;
====UNIX====&lt;br /&gt;
* simplest mechanisms, most usable&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* software that mediates all security decisions&lt;br /&gt;
* MULTICS designed to have a reference monitor, which was their ring system&lt;br /&gt;
* UNIX doesn’t really have one, processes (kind of) moderate security decisions together&lt;/div&gt;</summary>
		<author><name>Jessjohnson</name></author>
	</entry>
	<entry>
		<id>https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20664</id>
		<title>SystemsSec 2016W Lecture 4</title>
		<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20664"/>
		<updated>2016-02-04T15:11:06Z</updated>

		<summary type="html">&lt;p&gt;Jessjohnson: /* Jails */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Topics &amp;amp; Readings===&lt;br /&gt;
* chroot jails&lt;br /&gt;
* MULTICS&lt;br /&gt;
&lt;br /&gt;
====Jails====&lt;br /&gt;
* better version of chmod&lt;br /&gt;
* BSD mechanism, not really a Linux thing&lt;br /&gt;
* limiting hierarchy to make a non-root dir seem like the root dir, forces hierarchy to be duplicated so that nothing seems weird&lt;br /&gt;
* fake root user gets ‘jailed’ into subset of hierarchy, and doesn’t really have real root privileges&lt;br /&gt;
* process has a different root dir in kernel, but to the fake root user it still seems like the root dir&lt;br /&gt;
* one kernel space, multiple user spaces&lt;br /&gt;
* kind of like OS virtualization&lt;br /&gt;
&lt;br /&gt;
====DD-WRT====&lt;br /&gt;
* firmware for routers&lt;br /&gt;
* WRT54G LinkSys router with a Linux kernel on it&lt;br /&gt;
&lt;br /&gt;
====Proxy vs VPN tunneling====&lt;br /&gt;
* proxies are for HTTP specifically&lt;br /&gt;
* VPN is for any internet traffic&lt;br /&gt;
* TCP IP illustrated, to better understand networking&lt;br /&gt;
&lt;br /&gt;
====(Complex Security) Policies====&lt;br /&gt;
* &amp;quot;Suck, don’t make them.&amp;quot; - Anil, 2016.&lt;br /&gt;
* can’t approximate how humans approach information with logic systems&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* supposed to be a “grown up” OS&lt;br /&gt;
* first OS to take security seriously&lt;br /&gt;
* took a &amp;quot;shotgun approach&amp;quot; to security, too much generality&lt;br /&gt;
* implemented a ring system which was overly complicated&lt;br /&gt;
&lt;br /&gt;
====UNIX====&lt;br /&gt;
* simplest mechanisms, most usable&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* software that mediates all security decisions&lt;br /&gt;
* MULTICS designed to have a reference monitor, which was their ring system&lt;br /&gt;
* UNIX doesn’t really have one, processes (kind of) moderate security decisions together&lt;/div&gt;</summary>
		<author><name>Jessjohnson</name></author>
	</entry>
	<entry>
		<id>https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20653</id>
		<title>SystemsSec 2016W Lecture 4</title>
		<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_4&amp;diff=20653"/>
		<updated>2016-02-02T23:33:44Z</updated>

		<summary type="html">&lt;p&gt;Jessjohnson: Created page with &amp;quot;====Jails==== * better version of chmod * BSD mechanism, not really a Linux thing * limiting hierarchy to make a non-root dir seem like the root dir, forces hierarchy to be du...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;====Jails====&lt;br /&gt;
* better version of chmod&lt;br /&gt;
* BSD mechanism, not really a Linux thing&lt;br /&gt;
* limiting hierarchy to make a non-root dir seem like the root dir, forces hierarchy to be duplicated so that nothing seems weird&lt;br /&gt;
* fake root user gets ‘jailed’ into subset of hierarchy, and doesn’t really have real root privileges&lt;br /&gt;
* process has a different root dir in kernel, but to the fake root user it still seems like the root dir&lt;br /&gt;
* one kernel space, multiple user spaces&lt;br /&gt;
* kind of like OS virtualization&lt;br /&gt;
&lt;br /&gt;
====DD-WRT====&lt;br /&gt;
* firmware for routers&lt;br /&gt;
* WRT54G LinkSys router with a Linux kernel on it&lt;br /&gt;
&lt;br /&gt;
====Proxy vs VPN tunneling====&lt;br /&gt;
* proxies are for HTTP specifically&lt;br /&gt;
* VPN is for any internet traffic&lt;br /&gt;
* TCP IP illustrated, to better understand networking&lt;br /&gt;
&lt;br /&gt;
====(Complex Security) Policies====&lt;br /&gt;
* &amp;quot;Suck, don’t make them.&amp;quot; - Anil, 2016.&lt;br /&gt;
* can’t approximate how humans approach information with logic systems&lt;br /&gt;
&lt;br /&gt;
====MULTICS====&lt;br /&gt;
* supposed to be a “grown up” OS&lt;br /&gt;
* first OS to take security seriously&lt;br /&gt;
* took a &amp;quot;shotgun approach&amp;quot; to security, too much generality&lt;br /&gt;
* implemented a ring system which was overly complicated&lt;br /&gt;
&lt;br /&gt;
====UNIX====&lt;br /&gt;
* simplest mechanisms, most usable&lt;br /&gt;
&lt;br /&gt;
====Reference Monitor====&lt;br /&gt;
* software that mediates all security decisions&lt;br /&gt;
* MULTICS designed to have a reference monitor, which was their ring system&lt;br /&gt;
* UNIX doesn’t really have one, processes (kind of) moderate security decisions together&lt;/div&gt;</summary>
		<author><name>Jessjohnson</name></author>
	</entry>
	<entry>
		<id>https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_5&amp;diff=20562</id>
		<title>SystemsSec 2016W Lecture 5</title>
		<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_5&amp;diff=20562"/>
		<updated>2016-01-21T16:20:12Z</updated>

		<summary type="html">&lt;p&gt;Jessjohnson: /* Remote attacker, authenticated */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Class discussion: threat models and attacker goals&lt;br /&gt;
&lt;br /&gt;
==Local attacker==&lt;br /&gt;
&lt;br /&gt;
==Administrative attacker==&lt;br /&gt;
&lt;br /&gt;
==Remote attacker, authenticated==&lt;br /&gt;
&lt;br /&gt;
=== Group 3 ===&lt;br /&gt;
====Members====&lt;br /&gt;
* Dania Ghazal&lt;br /&gt;
* Ankush Varshneya&lt;br /&gt;
* Olivier Hamel&lt;br /&gt;
* Michael Aaya&lt;br /&gt;
* Ryan Morfield&lt;br /&gt;
* Daniel Vanderveen&lt;br /&gt;
* Jess Johnson&lt;br /&gt;
&lt;br /&gt;
====Example Scenario====&lt;br /&gt;
&#039;&#039;&#039;Targeted System&#039;&#039;&#039;&lt;br /&gt;
* CIA database - find out who killed Kennedy?&lt;br /&gt;
&#039;&#039;&#039;Attackers&#039;&#039;&#039;&lt;br /&gt;
* remote authenticators&lt;br /&gt;
* contractors (non CIA)&lt;br /&gt;
&#039;&#039;&#039;Goals&#039;&#039;&#039;&lt;br /&gt;
* “exfiltrating data”&lt;br /&gt;
* exfiltrate the CIA database to find out who killed Kennedy&lt;br /&gt;
&#039;&#039;&#039;Means&#039;&#039;&#039;&lt;br /&gt;
* someone at the CIA left a node.js server running in the background :)&lt;br /&gt;
* ssh credentials&lt;br /&gt;
* use outdated emacs (implementing a root privileged mail daemon) to inject a password into etc/passwd to escalate attacker’s privileges&lt;br /&gt;
* look around the system for more vulnerable/outdated services to exploit&lt;br /&gt;
* generate a race condition to create a file that you know a root user would create, then let the root user put their “sensitive data” into attacker’s file (such as files in /temp)&lt;br /&gt;
* social engineering - submit a help ticket to someone within the CIA to gain higher privileges for a seemingly innocent reason&lt;br /&gt;
====Attack Strategies====&lt;br /&gt;
&#039;&#039;&#039;Where are the Accessible Weaknesses?&#039;&#039;&#039;&lt;br /&gt;
* outdated services&lt;br /&gt;
* any service that lets attacker execute a task as another user&lt;br /&gt;
&#039;&#039;&#039;How Do You Attack Them?&#039;&#039;&#039;&lt;br /&gt;
* user privilege escalation&lt;br /&gt;
* abusing service vulnerabilities&lt;br /&gt;
&lt;br /&gt;
==Physical attacker, authenticated==&lt;br /&gt;
&lt;br /&gt;
==Physical attacker, unauthenticated==&lt;br /&gt;
&lt;br /&gt;
==Remote attacker, unauthenticated==&lt;/div&gt;</summary>
		<author><name>Jessjohnson</name></author>
	</entry>
	<entry>
		<id>https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_5&amp;diff=20561</id>
		<title>SystemsSec 2016W Lecture 5</title>
		<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=SystemsSec_2016W_Lecture_5&amp;diff=20561"/>
		<updated>2016-01-21T16:16:53Z</updated>

		<summary type="html">&lt;p&gt;Jessjohnson: /* Remote attacker, authenticated */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Class discussion: threat models and attacker goals&lt;br /&gt;
&lt;br /&gt;
==Local attacker==&lt;br /&gt;
&lt;br /&gt;
==Administrative attacker==&lt;br /&gt;
&lt;br /&gt;
==Remote attacker, authenticated==&lt;br /&gt;
&lt;br /&gt;
=== Group 3 ===&lt;br /&gt;
====Members====&lt;br /&gt;
* Dania Ghazal&lt;br /&gt;
* Ankush Varshneya&lt;br /&gt;
* Olivier Hamel&lt;br /&gt;
* Michael Aaya&lt;br /&gt;
* Ryan Morfield&lt;br /&gt;
* Daniel Vanderveen&lt;br /&gt;
* Jess Johnson&lt;br /&gt;
&lt;br /&gt;
====Example Scenario====&lt;br /&gt;
&#039;&#039;&#039;Targeted System&#039;&#039;&#039;&lt;br /&gt;
* CIA database - find out who killed Kennedy?&lt;br /&gt;
&#039;&#039;&#039;Attackers&#039;&#039;&#039;&lt;br /&gt;
* remote authenticators&lt;br /&gt;
* contractors (non CIA)&lt;br /&gt;
&#039;&#039;&#039;Goals&#039;&#039;&#039;&lt;br /&gt;
* “exfiltrating data”&lt;br /&gt;
* Exfiltrate the CIA database to find out who killed Kennedy&lt;br /&gt;
&#039;&#039;&#039;Means&#039;&#039;&#039;&lt;br /&gt;
* someone at the CIA left a node.js server running in the background :)&lt;br /&gt;
* ssh credentials&lt;br /&gt;
* use outdated emacs (implementing a root privileged mail daemon) to inject a password into etc/passwd to escalate attacker’s privileges&lt;br /&gt;
* look around the system for more vulnerable/outdated services to exploit&lt;br /&gt;
* generate a race condition to create a file that you know a root user would create, then let the root user put their “sensitive data” into attacker’s file (such as files in /temp)&lt;br /&gt;
* social engineering - submit a help ticket to someone within the CIA to gain higher privileges for a seemingly innocent reason&lt;br /&gt;
====Attack Strategies====&lt;br /&gt;
&#039;&#039;&#039;Where are the Accessible Weaknesses?&#039;&#039;&#039;&lt;br /&gt;
* outdated services&lt;br /&gt;
* any service that lets attacker execute a task as another user&lt;br /&gt;
&#039;&#039;&#039;How Do You Attack Them?&#039;&#039;&#039;&lt;br /&gt;
* user privilege escalation&lt;br /&gt;
* abusing service vulnerabilities&lt;br /&gt;
&lt;br /&gt;
==Physical attacker, authenticated==&lt;br /&gt;
&lt;br /&gt;
==Physical attacker, unauthenticated==&lt;br /&gt;
&lt;br /&gt;
==Remote attacker, unauthenticated==&lt;/div&gt;</summary>
		<author><name>Jessjohnson</name></author>
	</entry>
</feed>