commit

diff --git a/en/workshops.html b/en/workshops.html
index 7b08d097a8f1505259ae1b05731704e7b0ff68d9..e15effa4e5eb2bf205a0144be355ebdd7fdc07c2 100644 (file)
--- a/en/workshops.html
+++ b/en/workshops.html
@@ -157,64 +157,19 @@ step towards protecting their privacy with free software.
                </section>
 
 
-<!-- ~~~~~~~~~ Section 3: Sign Keys  ~~~~~~~~~ -->
+<!-- ~~~~~~~~~ Section 4: Explain the pitfalls  ~~~~~~~~~ -->
                <section class="row" id="section4">
                        <div>
                                        <!-- ~~~~~~~~~ section introduction: interspersed text  ~~~~~~~~~ -->
                                <div class="section-intro">
-                                               <h2><em>#3</em> Sign Keys</h2>
-                                               <p>Emphasize the distinction between trusting a person subjectively, and seeing whose keys they've signed objectively. Without a proper understanding of trust, the beautiful transative trust properties of the web of trust are lost. Since trust is an internal and subjective thing, it's unnecessary for participants to share how much they trust another participant with anyone else.</p>
-
-<p>Have the participants download each other's keys, read out their own fingerprints, and present their IDs to each other. Help participants navigate the interface to sign each other's keys, and encourage participants to assign each other trust levels if they already know each other.</p>
+                                               <h2><em>#4</em> Explain the pitfalls</h2>
+                                               <p>Remind participants that encryption works only when it's explicitly used; they won't be able to send an encrypted email to someone who hasn't already set up encryption. Also remind participants to double-check the encryption icon before hitting send, and that subjects and timestamps are never encrypted. See Email Self-Defense's Security Tips subsection for more information.</p>
+                                               <p>Advocate for free software, because without it, we can't <a href="https://www.fsf.org/bulletin/2013/fall/how-can-free-software-protect-us-from-surveillance">meaningfully resist invasions of our digital privacy and autonomy</a>. Explain the <a href="https://www.gnu.org/proprietary/proprietary.html">dangers of running a proprietary system</a>, and why GnuPG <a href="https://www.gnu.org/philosophy/proprietary-surveillance.html">can't begin to mitigate them</a>.</p>
 
 
 
                                </div><!-- End .section-intro -->
 
-                               <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
-                               <div id="step-4a" class="step">
-                                       <div class="sidebar">
-                                               <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section4-web-of-trust.png" alt="Section 4: Web of Trust"></p>
-                                       </div><!-- /.sidebar -->
-                                       <div class="main">
-                                               <h3><em>Step 4.a</em> Sign a key</h3>
-                                               <p>In your email program's menu, go to Enigmail → Key Management.</p>
-                                               <p>Right click on Edward's public key and select Sign Key from the context menu.</p>
-                                               <p>In the window that pops up, select "I will not answer" and click ok.</p>
-                                               <p>Now you should be back at the Key Management menu. Select Keyserver → Upload Public Keys and hit ok.</p>
-                                               <p class="notes">You've just effectively said "I trust that
-Edward's public key actually belongs to Edward." This doesn't mean much
-because Edward isn't a real person, but it's good practice.</p>
-
-
-                                               <!--<div id="pgp-pathfinder">
-                                                       <form enctype="application/x-www-form-urlencoded" action="/mk_path.cgi" method="get">
-                                                               <p><strong>From:</strong> <input type="text" placeholder="xD41A008"  name="FROM"></p>
-                                                               <p><strong>To:</strong> <input type="text" placeholder="50BD01x4" name="TO"></p>
-                                                               <p class="buttons"><input type="submit" value="trust paths" name="PATHS"> <input type="reset" value="reset" name=".reset"></p>
-                                                       </form>
-                                               </div><!-- End #pgp-pathfinder -->
-
-                                       </div><!-- End .main -->
-                               </div><!-- End #step-4a .step -->
-
-                               <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
-                               <div id="step-sign_real_keys" class="step">
-                                       <div class="main">
-                                               <h3><em>Important:</em> check people's identification before signing their keys</h3>
-                                               <p>Before signing a real person's key, always make sure it
-actually belongs to them, and that they are who they say they are. Ask
-them to show you their ID (unless you trust them very highly) and their
-public key fingerprint -- not just the shorter public key ID, which
-could refer to another key as well. In Enigmail, answer honestly in the
-window that pops up and asks "How carefully have you verified that the
-key you are about to sign actually belongs to the person(s) named
-above?".</p>
-                                       </div><!-- End .main -->
-                               </div><!-- End #step-sign_real_keys .step-->
-
-
-
                        </div>
                </section><!-- End #section4 -->