removed redunant titles. updated todo.

levels/02 Spoofs/spoofs01.html

@@ -1,6 +1,4 @@
 
-<h1>Spoofs Level 1</h1>
-
 <p>The srcip and dstip headers can be easily changed to specify different source and destination addresses.
 In the previous levels, we saw that changing the destination address changed the direction in which the packet was sent.
 Note, however, that we did not need to specify a source address. In fact, routers do not take into account where

levels/02 Spoofs/spoofs02.html

@@ -1,4 +1,3 @@
-<h1>Spoofs Level 2</h1>
 
 <p>This level contains several devices connected to a <strong>switch</strong>. A <strong>switch</strong> is similar
 to a router, but it starts out with an empty <strong>routing table</strong>. Over time, it learns where to send

levels/03 DoS/dos01.html

@@ -1,6 +1,4 @@
 
-<h1>DoS Level 1</h1>
-
 <p>A <strong>Denial of Service (DoS)</strong> attack overwhelms a computer or server by flooding it with <strong>packets</strong>.
 The purpose of <strong>DoS</strong> attacks are to make a system (such as Google) unavailable for others to use.
 This often distracts the administrators of the system and allows an attacker to exploit it in different ways and

levels/03 DoS/dos02.html

@@ -1,6 +1,4 @@
 
-<h1>DoS Level 2</h1>
-
 <p>A server or computer can protect itself by blocking malicious computers using a <strong>firewall</strong>. A
 <strong>firewall</strong> keeps a list of "bad" source addresses and drops all packets that come from an address on
 the list. In this example, Google has learned from the previous attack that Alice is a malicious user and has set up

levels/03 DoS/dos03.html

@@ -1,6 +1,4 @@
 
-<h1>DoS Level 3</h1>
-
 <p>The router in this level responds to a special type of ping, called a "Broadcast ping".  When a router receives a packet that is addressed
 to the broadcast address, it replicates it and sends it to <em>all</em> the machines on the network.
 

levels/04 Attacks/attacks01.html

@@ -1,6 +1,4 @@
 
-<h1>Attacks Level 1</h1>
-
 <p>In this level, you can see an example of Bob sending Alice an <strong>encryption key</strong> in order to protect 
 their messages.  However, their simple protocol is vulnerable to a <strong>man-in-the-middle</strong> attack.
 

levels/04 Attacks/attacks02.html

@@ -1,6 +1,4 @@
 
-<h1>Attacks Level 1</h1>
-
 <p>In this level, Alice's Internet browsing is being <strong>censored.</strong> She can browse an <strong>allowed site</strong>, but the censor will drop any packets to a <strong>blocked site</strong>.
 
 <p>One way to evade censorship is to make an intermediate connection to a <strong>proxy server</strong>. This server will take packets that are destined to it and redirect them to the blocked site. Since the censor can only see the link between Alice and the proxy, it does not know which site Alice is browsing through it.

todo

@@ -1,15 +1,8 @@
 blocking
-- remove CSS lines from beginning of each level
-- update sprites & layouts in level files
-- update ui-specific mentions in level descrips
-- convert triggers in level files to arrays
-- update nextLevel in each file
 - update "you win" dialog to handle no nextLevel property
 - prettier level listing
 - resize game on resize viewport (attempt at this at top of ui.js but it's laggy)
-- device scripts (?list)
 - method to work on test levels
-- hosted version on DO
 
 nice to have
 - screenshots for level selector?
@@ -19,11 +12,8 @@ nice to have
 - only preload used device sprites
 - move levels to database
 - level editor
-- more variety in device sprites
-- slower intro/learning levels
 
 long term
-- licensing
 - non-php version
 --- load json/html via ajax
 --- remove login system
@@ -38,4 +28,3 @@ level ideas
 - privacy (see ISPs, who can read data, etc)
 - how protocols work (HTTP, DNS, email, DHCP...)
 
-test3