From d8dd09860c0523e5dda94c8ba194995fe236a92c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Todor=20Kondi=C4=87?= <todor.kondic@uni.lu>
Date: Tue, 24 Mar 2020 04:06:18 +0100
Subject: [PATCH] Add slides_intro_3.md

---
 .../slides/ssh_intro_3.md                     | 39 +++++++++++++++++++
 1 file changed, 39 insertions(+)
 create mode 100644 2020/2020-02-15_gnuLinuxCourse/slides/ssh_intro_3.md

diff --git a/2020/2020-02-15_gnuLinuxCourse/slides/ssh_intro_3.md b/2020/2020-02-15_gnuLinuxCourse/slides/ssh_intro_3.md
new file mode 100644
index 00000000..69f68143
--- /dev/null
+++ b/2020/2020-02-15_gnuLinuxCourse/slides/ssh_intro_3.md
@@ -0,0 +1,39 @@
+# Accessing Computers over Network (Securely)
+
+* Normally, very few ports are open on a modern (LCSB) server
+
+<!-- .element: class="fragment" -->
+* In addition, the communication to and from ports is typically encrypted
+  - Why? Because, between the sender and a recepient there is a whole
+    jungle of transfer network nodes, each of which is potentially
+    [p(owned)][1] by an adversary
+	
+  <!-- .element: class="fragment" -->
+  - For a thorough introduction, see [this set of EFF articles][2]
+  
+  <!-- .element: class="fragment" -->
+  - _Transparency is a virtue of the naive_ 
+	- remember, we're not doing politics
+	
+	<!-- .element: class="fragment" -->
+
+  <!-- .element: class="fragment" -->
+  
+<!-- .element: class="fragment" -->
+* In the context of todays lecture, one type of encrypted
+  communication protocol will help us solve three fundamental
+  questions
+  - How to securely log in to a server?
+  
+  <!-- .element: class="fragment" -->
+  - How to securely interact with a server?
+  
+  <!-- .element: class="fragment" -->
+  - How to securely exchange any kind (and amount) of data with a server?
+  
+  <!-- .element: class="fragment" -->
+  
+<!-- .element: class="fragment" -->
+		
+[1]: https://en.wikipedia.org/wiki/Zombie_(computing)
+[2]: https://ssd.eff.org/
-- 
GitLab