From 29b1d0e32c524d1c3e794d4d567ebde2496e8a23 Mon Sep 17 00:00:00 2001 From: Sean Leonard Date: Mon, 11 Nov 2013 18:52:17 -0800 Subject: Add "hard problems" section --- overview/en.html | 89 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 89 insertions(+) diff --git a/overview/en.html b/overview/en.html index 547ecd0..cda9e27 100644 --- a/overview/en.html +++ b/overview/en.html @@ -40,6 +40,95 @@ +
+
+

Crypto is Hard

+

But wait, you said...

+

Encryption should be
simple to provide and easy to use

+

So...

+
+
+

Solve the Hard Problems

+
+

The “Big 7”

+
    +
  1. Authenticity problem
    2. +
  2. Meta-data problem
    3. +
  3. Asynchronous problem
    4. +
  4. Group problem
    5. +
  5. Resource problem
    6. +
  6. Availability problem
    7. +
  7. Update problem
    8. +
+
+
+
+

Authenticity problem

+
Public key validation is very difficult for users to manage, but without it you cannot have confidentiality
+
  • Nicknym - auto discovery and validation of public keys, transparently!
    • +
    +
    +

    Meta-data problem

    +
    Existing protocols are vulnerable to meta-data analysis, even though meta-data is often much more sensitive than content
    +
    +
      +
    • Downgrade-proof DNSSEC/DANE
      • +
    +

    With one or more opportunistic schemes:

    +
      +
    • Auto alias pairs
      • +
    • Onion routing headers
      • +
    • Third party dropbox
      • +
    • Mixmaster with signatures
      • +
    +
    +
    +
    +

    Asynchronous problem

    +
    For encrypted communication, you must currently choose between forward secrecy or the ability to communicate asynchronously
    +
    +
      +
    • OpenPGP vs. OTR
      • +
    • Stop-gap: Layer forward secret transport atop OpenPGP
      • +
    • Long term: Collaborate with others to create new encryption protocol standards
      • +
    +
    +
    +
    +

    Group problem

    +
    In practice, people work in groups, but public key cryptography doesn’t
    +
      +
    • First we...ummm
      • +
    • Interesting work in secure file backup/sync/sharing (e.g. Wuala and SpiderOak) +
    • Proxy re-encryption
      • +
    • Ring signatures
      • +
    +
    +
    +

    Resource problem

    +
    There are no open protocols to allow users to securely share a resource
    +
      +
    • Yup, still got nothin' :/
      • +
    • "Read-write-web", meet ["Group problem" solution here] +
    • Again, possibilities from file sync (Lazy Revocation and Key Regression) +
    +
    +
    +

    Availability problem

    +
    People want to smoothly switch devices, and restore their data if they lose a device, but this very difficult to do securely
    +
  • Soledad - Synchronization of Locally Encrypted Documents Among Devices
    phew! we weren't out of ideas!
    • +
    +
    +

    Update problem

    +
    Almost universally, software updates are done in ways that invite attacks and device compromises
    +
  • Thandy (thanks, Tor!)
    • +
    +
    + +
    +

    So, what have you got?

    +
    +

    Services

    Encrypted Internet Proxy aka VPN

    -- cgit v1.2.3