From f639bad85682c50f504264a93c674578710234da Mon Sep 17 00:00:00 2001 From: Adam Leibson Date: Tue, 18 Aug 2015 17:52:12 -0400 Subject: [PATCH] commit --- en/workshops.html | 44 ++++++-------------------------------------- 1 file changed, 6 insertions(+), 38 deletions(-) diff --git a/en/workshops.html b/en/workshops.html index 7bf3256..7b08d09 100644 --- a/en/workshops.html +++ b/en/workshops.html @@ -142,51 +142,19 @@ step towards protecting their privacy with free software. - +
-

#2 Follow The Guide

-

Have the participants work through the Email Self-Defense guide a step at a time on their own computers. Make sure all participants complete each step before the group moves on to the next step. Talk about each step, but be sure not to overload the participants with minutia. Pitch the bulk of your instruction to the least tech-savvy participants. Consider holding a secondary workshop afterwards for the outliers in either direction.

+

#3 Follow the guide as a group

+

Work through the Email Self-Defense guide a step at time as a group. Talk about the steps in detail, but make sure not to overload the participants with minutia. Pitch the bulk of your instructions to the least tech-savvy participants. Make sure all the participants complete each step before the group moves on to the next one. Consider facilitating secondary workshops afterwards for people that had trouble grasping the concepts, or those that grasped them quickly and want to learn more.

+

Even powerful surveillance systems can't break private keys when they're protected by lengthy Diceware passphrases. Make sure participants use the Diceware method, if dice are available. Stress the importance of eventually destroying the piece of paper the Diceware password is written on, and make sure all the participants back up their revocation certificates.

+

In step 2, make sure the participants upload their keys to the same keyserver so that they can immediately download each other's keys later (sometimes there is a delay in synchronization between keyservers). During Step 3, give the participants the option to send encrypted messages to each other instead of or as well as Edward. Similarly, in Step 4, encourage the participants to sign each other's keys.

- - -
-
-

Try it out.

-
-
-

Step 2.a Public and Private Keys key

-

Make sure all the participants have a conceptual understanding of the relationship between public and private keys in a keypair. It's normal for people to not understand public-key cryptography on the first try. Use analogies to help explain the concept.

- -
-
- - -
-
-

Section 5: Use it Well

-
-
-

Step 2.b Diceware and Passphrases

-

Sufficiently strong passphrases can't easily be brute forced, and thus protect the private key even if it falls into the wrong hands. Recommend participants use the diceware method , and have dice and the wordlist available for them to use. Participants who choose to use diceware should keep their passphrase with them at all at all times until they memorize it. Stress the importance of creating and backing up revocation certificates, especially to participants who write down their diceware passphrases.

- -
-

Disclaimer

-
-
Diceware and Licensing
-
Something here about diceware's relationship with free software, or something.
-
-
- -
-
- -
-
+ -- 2.25.1