Difference between revisions of "GPG guide/Infographics"

From LibrePlanet
Jump to: navigation, search
(Release Candidate)
 
(24 intermediate revisions by 2 users not shown)
Line 1: Line 1:
=General Ideas=
+
=Text=
* Narrative structure, like a comic. I imagine the story it tells is: there are two people trying to communicate, but they are being surveilled. Then they go through the process of setting up GPG, and they they communicate securely. This give us a a good way to explain keys, keyservers, encryption and sisgning.
+
===Panel 1: Email Self-Defense===
*** First  panel explains the problem and has a picture of many characters (or  maybe just the original two) sending email to each other that's getting  intercepted and little expressions, symbols or speech bubbles that shows  all the ways this hurts them. Text refers to the problems inherent with  unencrypted meail (surveillance, insecrutiy, chilling free speech, repressing dissidents etc).
+
Internet surveillance violates our fundamental rights and makes free speech risky. But we're far from helpless to do something about it.
*** Then  some kind of thing that's like "you can do something about it" You  don't have to use it all the time, but knowing how is important, and  here are some times to use it. Makes you more secure from surveillance  and private companies and in general.
+
 
* Prominently features URL of the guide, which we haven't determined yet
+
===Panel 2: No Title===
* Explains the basics elements of the GPG system: two people communicating, keyserver, keys, imaginary attacker who wants to surveil
+
The password protecting your email is only a thin layer of security that can't protect against the battering ram of sophisticated surveillance systems.
* Makes sense as a standalone sharable infographic, also makes sense as the introduction to the guide and a visual aid to understanding the basics of how the GPG system works.
+
 
* Should grip people into wanting to participate and show them why this is important, in addition to (or instead of?) just showing them how encryption works. Overall message is "you've heard of this problem, but did you know you can do something about it? Here's how. People will share because it feels like (part of) a solution to a problem that is weighing on them
+
Each message passes through many computer systems on the way to its destination. Surveillance agencies take advantage of this to read millions and millions of emails.
* This is the closest thing I've seen to what I'm imagining: <http://flossmanuals.net/thunderbird-workbook/>, but it is of course less comprehensive. There's another one a few pages in to this guide, too.
+
 
* If we have extra time, we should make an infographic to help people understand the Web of Trust
+
Even if you have nothing to hide, when you send normal email, the people you talk to are being exposed as well.
* Would be good to have something that gives a visual impression of the network effect of people using GPG (which causes it to make more sense for still more people to join), like an expanding network.
+
 
* A big part of this is that we want people to incorporate their GPG key into their online identity. Perhaps at some point in the infographic, it shows a drawing of a person's social media profile or website or email signature in which it shows that they are publicly displaying their GPG key.
+
===Panel 3: Take Your Privacy Back with GnuPG [get rid of "With GnuPG" if it's awkward-looking]===
 +
All you need is a simple program called GnuPG. It encrypts your email into a code that only the right people can read.
 +
 
 +
GnuPG runs on pretty much any computer or smartphone. It's freely licensed and costs no money. Each user has a unique public key and private key, which are random strings of numbers.
 +
 
 +
===Panel 4: Your Public Key===
 +
Your public key isn't like a physical key, because it's stored in the open on a Website. People download it and use it, along with GnuPG, to encrypt emails they send to you.
 +
 
 +
===Panel 5: Your Private Key===
 +
Your private key is more like a physical key, because you keep it to yourself (on your computer). You use GnuPG and your private key to decode encrypted emails other people send to you.
 +
 
 +
===Panel 6: No Title===
 +
If an email encrypted with GnuPG falls into the wrong hands, it'll just look like nonsense. Without the real recipient's private key, it's almost impossible to read it.
 +
 
 +
To the real recipient, it just open up like a normal email. Easy!
 +
 
 +
The sender and recipient are both safer now. Even if this email doesn't have any private information, being encrypted makes it gum up bulk surveillance systems. Take that, surveillance!
 +
 
 +
===Panel 7: No Title===
 +
To protect ourselves from surveillance, we need to learn when to use encryption and start sharing our public keys whenever we share email addresses.
 +
 
 +
Thousands of people already use GnuPG, including activists, journalists, whistleblowers and everyday folks. Each person using it makes our community stronger, and shows surveillance agencies that we are ready to fight back.
 +
 
 +
===Panel 8: No Title===
 +
[giant text]Teach yourself email self defense. Learn GnuPG in FIXME minutes at EmailSelfDefense.FSF.org
 +
 
 +
[if the URL looks like a word soup, you could make each word in EmailSelfDefense a different color]
 +
 
 +
[FREE SOFTWARE FOUNDATION logo somewhere down here]
  
=Text=
+
===Free software textbox - I want to add this somewhere===
* Educate people about how free software is better for security and privacy
+
GnuPG is '''freely licensed software'''; it's completely transparent and anyone can copy it or make their own version. This makes it safer from surveillance than '''proprietary software''' (like Windows or Word). Learn more at FSF.org.
* Educate people about encryption and how it can and cannot protect them
+
 
* Take credit for GPG as part of the GNU Project
+
=Illustrated mock-up=
* Raise awareness and stoke outrage about illegal spying by corporations and governments
+
 
 +
[[File:Infog-mockup.png|500px|thumb|center|Infographic mockup]]
 +
 
 +
'''!!Colors are not final!!''' These are just to illustrate the division between panels.
 +
Final colorscheme will be a lot lighter and easier on the eyes, see [http://media-cache-ec0.pinimg.com/736x/f6/f6/c9/f6f6c90e9720302e6a472375f34cfd14.jpg this] for an example of what we're thinking color-wise.
 +
 
 +
Notes:
 +
 
 +
* Panel 1: The agent on the header is probably not the right choice (you don't listen to a written message, you read it). Waiting for final intro text.
 +
* Panel 2: Image represents stereotypical neighborhood at night, with two residential homes and the snoopers' HQ in the middle. Bottom floor is an engineer on a supercomputer filtering through the snooped messages. Top floor is a female supervisor reading a printout and speaking to someone on the phone. The idea is to represent that they're not only reading the messages, they're acting on the obtained info. Building probably needs to be horizontal (with two rooms) to save vertical space. One of the people in the houses (sender) should be represented as a woman too. Supervisor office has a manager desk with an eagle logo on top of it, representing an "imperial" entity, not just the US -- see latest news about Germany wanting to increase funds for online spying.
 +
* Panel 3: GnuPG is represented as the "lockbot" with some mechanical/electronic features. Text should probably already mention the keypair generation.
 +
* Panel 4: Public keys: Text could benefit by mentioning this key should be shared. Right illustration could also get snippet explaining that GnuPG just needs the message and the recipient's public key to encrypt it.
 +
* Panel 5: Same as panel 4 wrt both texts: text should make it clear you should treat this as a "traditional" key that you shouldn't share with anyone. Ideal if we can have a snippet on the right describing the decryption process.
 +
* Panel 6: Unlike panel 2, this one represents daytime (brighter future). Encrypted boxes are flowing through the pipes; snooper eye is confused, engineer gets an error ("permission denied?"), supervisor's still on the phone cursing and looking at garbled text coming out the printer. Sender and recipient look exactly the same (life goes on as usual, but now they're safer).
 +
* Panel 7: Illustrated e-mail signature with pubkey. GnuPG holds both keys, saying "I'll keep your secrets!"
 +
* Panel 8: Closing note, reference to guide and all other extra info needed (please provide!)
 +
 
 +
=Pre-color version=
 +
 
 +
[[File:Infog-precolor.png|500px|thumb|center|Infographic mockup]]
 +
 
 +
Notes:
 +
* Green is just the placeholder color. Red was used to show that there will be a visual cue for the connection flow.
 +
* The final piece will be colored: the scenes with the users and agents will be full color, while the others will run a soft color palette, according to the needs of each panel. We're thinking of coloring the public key panel blue, and the private key panel red, to emphasize the difference between both.
 +
* Both male characters are currently missing hair -- at least one of them will get a hairdo in order to avoid confusion.
 +
* Some text emphasis (bold, underline) might be in order in parts of the keypair text so that the key points are clear.
 +
* Probably the "GnuPG is free software" panel could go one step up, before the "To protect ourselves" panel?
 +
* The "e-mail signature" illustration with the public key is somewhat lacking; it is actually a fingerprint (though introducing the term "fingerprint" in this infographic might be confusing) and maybe we can instead find another way to represent large-scale sharing of public keys. What's your thoughts? Maybe the text can also reflect this, with more examples besides sharing pubkeys in e-mail sigs?
 +
 
 +
=Release Candidate=
 +
 
 +
[[File:Infog-footerless.png|500px|thumb|center|Almost ready to go out, review and edit footer]]

Latest revision as of 18:14, 4 June 2014

Text

Panel 1: Email Self-Defense

Internet surveillance violates our fundamental rights and makes free speech risky. But we're far from helpless to do something about it.

Panel 2: No Title

The password protecting your email is only a thin layer of security that can't protect against the battering ram of sophisticated surveillance systems.

Each message passes through many computer systems on the way to its destination. Surveillance agencies take advantage of this to read millions and millions of emails.

Even if you have nothing to hide, when you send normal email, the people you talk to are being exposed as well.

Panel 3: Take Your Privacy Back with GnuPG [get rid of "With GnuPG" if it's awkward-looking]

All you need is a simple program called GnuPG. It encrypts your email into a code that only the right people can read.

GnuPG runs on pretty much any computer or smartphone. It's freely licensed and costs no money. Each user has a unique public key and private key, which are random strings of numbers.

Panel 4: Your Public Key

Your public key isn't like a physical key, because it's stored in the open on a Website. People download it and use it, along with GnuPG, to encrypt emails they send to you.

Panel 5: Your Private Key

Your private key is more like a physical key, because you keep it to yourself (on your computer). You use GnuPG and your private key to decode encrypted emails other people send to you.

Panel 6: No Title

If an email encrypted with GnuPG falls into the wrong hands, it'll just look like nonsense. Without the real recipient's private key, it's almost impossible to read it.

To the real recipient, it just open up like a normal email. Easy!

The sender and recipient are both safer now. Even if this email doesn't have any private information, being encrypted makes it gum up bulk surveillance systems. Take that, surveillance!

Panel 7: No Title

To protect ourselves from surveillance, we need to learn when to use encryption and start sharing our public keys whenever we share email addresses.

Thousands of people already use GnuPG, including activists, journalists, whistleblowers and everyday folks. Each person using it makes our community stronger, and shows surveillance agencies that we are ready to fight back.

Panel 8: No Title

[giant text]Teach yourself email self defense. Learn GnuPG in FIXME minutes at EmailSelfDefense.FSF.org

[if the URL looks like a word soup, you could make each word in EmailSelfDefense a different color]

[FREE SOFTWARE FOUNDATION logo somewhere down here]

Free software textbox - I want to add this somewhere

GnuPG is freely licensed software; it's completely transparent and anyone can copy it or make their own version. This makes it safer from surveillance than proprietary software (like Windows or Word). Learn more at FSF.org.

Illustrated mock-up

Infographic mockup

!!Colors are not final!! These are just to illustrate the division between panels. Final colorscheme will be a lot lighter and easier on the eyes, see this for an example of what we're thinking color-wise.

Notes:

  • Panel 1: The agent on the header is probably not the right choice (you don't listen to a written message, you read it). Waiting for final intro text.
  • Panel 2: Image represents stereotypical neighborhood at night, with two residential homes and the snoopers' HQ in the middle. Bottom floor is an engineer on a supercomputer filtering through the snooped messages. Top floor is a female supervisor reading a printout and speaking to someone on the phone. The idea is to represent that they're not only reading the messages, they're acting on the obtained info. Building probably needs to be horizontal (with two rooms) to save vertical space. One of the people in the houses (sender) should be represented as a woman too. Supervisor office has a manager desk with an eagle logo on top of it, representing an "imperial" entity, not just the US -- see latest news about Germany wanting to increase funds for online spying.
  • Panel 3: GnuPG is represented as the "lockbot" with some mechanical/electronic features. Text should probably already mention the keypair generation.
  • Panel 4: Public keys: Text could benefit by mentioning this key should be shared. Right illustration could also get snippet explaining that GnuPG just needs the message and the recipient's public key to encrypt it.
  • Panel 5: Same as panel 4 wrt both texts: text should make it clear you should treat this as a "traditional" key that you shouldn't share with anyone. Ideal if we can have a snippet on the right describing the decryption process.
  • Panel 6: Unlike panel 2, this one represents daytime (brighter future). Encrypted boxes are flowing through the pipes; snooper eye is confused, engineer gets an error ("permission denied?"), supervisor's still on the phone cursing and looking at garbled text coming out the printer. Sender and recipient look exactly the same (life goes on as usual, but now they're safer).
  • Panel 7: Illustrated e-mail signature with pubkey. GnuPG holds both keys, saying "I'll keep your secrets!"
  • Panel 8: Closing note, reference to guide and all other extra info needed (please provide!)

Pre-color version

Infographic mockup

Notes:

  • Green is just the placeholder color. Red was used to show that there will be a visual cue for the connection flow.
  • The final piece will be colored: the scenes with the users and agents will be full color, while the others will run a soft color palette, according to the needs of each panel. We're thinking of coloring the public key panel blue, and the private key panel red, to emphasize the difference between both.
  • Both male characters are currently missing hair -- at least one of them will get a hairdo in order to avoid confusion.
  • Some text emphasis (bold, underline) might be in order in parts of the keypair text so that the key points are clear.
  • Probably the "GnuPG is free software" panel could go one step up, before the "To protect ourselves" panel?
  • The "e-mail signature" illustration with the public key is somewhat lacking; it is actually a fingerprint (though introducing the term "fingerprint" in this infographic might be confusing) and maybe we can instead find another way to represent large-scale sharing of public keys. What's your thoughts? Maybe the text can also reflect this, with more examples besides sharing pubkeys in e-mail sigs?

Release Candidate

Almost ready to go out, review and edit footer