--- a/Overview-UseCases.xml Thu Dec 06 18:21:51 2012 -0500
+++ b/Overview-UseCases.xml Mon Dec 10 09:52:15 2012 -0500
@@ -308,20 +308,36 @@
[<a href="#digest">DIGEST</a> | <a href="#keycall">KEYCALL</a> | <a href="#verify">VERIFY</a>]</p>
</div>
<div id='encrypt' class='section'>
- <h3>Mitch Turns 21: Encrypted Communications</h3>
- <p>Mark wishes to post pictures of Mitch's 21st birthday party to a social network that allows confidential and encrypted communication between members, but wishes to ensure that these pictures are safe from prying eyes -- more importantly, he wants them to be indecipherable digital data for everyone except Mitch. Mark can do the following: </p>
- <ol>
- <li><p>He can encrypt the photos with a key he generates for the occasion. [<a href="#derive">DERIVE</a> | <a href="#encrypt">ENCRYPT</a>]</p></li>
- <li><p>He can communicate with others on the network about the key and share the encrypted photos. [<a href="#keyex">KEYEX</a> | <a href="#encrypt-pki">ENCRYPT-PKI</a>] </p></li>
- <li><p>He can receive confidential communication from Mitch about the pictures via encrypted messages that are virtually impossible to read by any other entity than Mark. [<a href="#verify">VERIFY</a> | <a href="#decrypt-pki">DECRYPT-PKI</a>]</p></li>
- </ol>
+ <h3>Fostering Encrypted Communications</h3>
+ <p>Tantek wishes to communicate with Ryan securely. Moreover, Tantek wishes to use an email web application (EWA) provided by a third party, which is a web site that allows users who have accounts to set up email accounts of their own choosing -- that is, users can enter in existing POP/IMAP/SMTP username and password credentials, or simply use an email address provided by the EWA.</p>
+ <p>Ryan provides a PGP key on his website, encoded in the relevant conventions. For instance, he uses microformats where relevant, and follows the common practice of including a Base64 "blob" that represents his public key.</p>
+ <div class="example">
+ <p>Ryan uses the hCard format to encapsulate contact information with some semantic annotation within the markup of his webpage. Within the hCard, he does something like this:</p>
+ <x:codeblock language="es">
+
+<span class="key">
+-----BEGIN PGP PUBLIC KEY BLOCK-----
+Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
+Comment: GPGTools - http://gpgtools.org
+
+nQENBE4sjPMBCAC0ublKDnsdwD9B71bygmwVxn3hX6zw4H1Qlc6wPc0/OepjqVyq
+...
+-----END PGP PUBLIC KEY BLOCK-----
+</span>
+ </x:codeblock>
+<p>The ellipsis have been added for brevity.</p>
+ </div>
+<p>Logging on to EWA, Tantek may find UI that prompts him to enter in Ryan's hCard path. Tantek does so, and EWA then begins the process of importing Ryan's PGP key. In order to do so, it must first "scrub" the key format to be in one of the accepted import formats of the WebCrypto API.</p>
+<div class="example">
+<p>// TODO Enter sample code for importing public key.</p>
+</div>
</div>
<div id='realtime-messaging' class='section'>
<h3>Off The Record Real Time Messaging</h3>
- <p>David and Nadim wish to have an "Off The Record" chat in real time, completely between them, and in text, including the ability to share digital data such as photographs. They log on to a chat server that serves up web content, and connect to each other's machines directly. The server merely serves up the chat client necessary, and does not log their conversation (and in fact cannot). David and Nadim need to:</p>
+ <p>David and Nadim wish to have an "Off The Record" chat in real time, completely between them, and in text, including the ability to share digital data such as photographs. They log on to a chat server, and connect to each other's machines directly. The server merely serves up the UI for the chat client, and does not log their conversation (and in fact, cannot). David and Nadim need to:</p>
<ul>
- <li><p>Be assured that they are who they claim they are. [<a href="#decrypt">DECRYPT</a> | <a href="#decrypt-pki">DECRYPT-PKI</a> | <a href="#encrypt">ENCRYPT</a> | <a href="#encrypt-pki">ENCRYPT-PKI</a>] </p></li>
- <li><p>Be assured that during a conversation, messages sent back and forth are unmodified. [<a href="#random">RANDOM</a> | <a href="#encrypt">ENCRYPT</a> | <a href="#decrypt">DECRYPT</a>] </p></li>
+ <li><p>Be assured that they are who they claim they are. [<a href="#sign">SIGN</a> | <a href="#verify">VERIFY</a> | <a href="#decrypt">DECRYPT</a> | <a href="#decrypt-pki">DECRYPT-PKI</a> | <a href="#encrypt">ENCRYPT</a> | <a href="#encrypt-pki">ENCRYPT-PKI</a>] </p></li>
+ <li><p>Be assured that during a conversation, messages sent back and forth are unmodified. [<a href="#encrypt">ENCRYPT</a> | <a href="#decrypt">DECRYPT</a>] </p></li>
<li><p>Be assured that after the conversation, the contents of the conversation cannot be determined. [???] </p></li>
</ul>
--- a/Overview.html Thu Dec 06 18:21:51 2012 -0500
+++ b/Overview.html Mon Dec 10 09:52:15 2012 -0500
@@ -113,7 +113,7 @@
<div id="toc">
<h2>Table of Contents</h2>
- <div class="toc"><ul><li><a href="#introduction">1. Introduction</a></li><li><a href="#requirements">2. Requirements</a></li><li><a href="#scenarios">3. Use Case Scenarios</a><ul><li><a href="#banking-korea">3.1. Banking Transactions</a></li><li><a href="#video-service">3.2. Dr. What: Video Service</a></li><li><a href="#data-integrity">3.3. Code Sanctity and Bandwidth Saver</a></li><li><a href="#encrypt">3.4. Mitch Turns 21: Encrypted Communications</a></li><li><a href="#realtime-messaging">3.5. Off The Record Real Time Messaging</a></li><li><a href="#savemystuff">3.6. Documents In the Cloud</a></li></ul></li></ul></div>
+ <div class="toc"><ul><li><a href="#introduction">1. Introduction</a></li><li><a href="#requirements">2. Requirements</a></li><li><a href="#scenarios">3. Use Case Scenarios</a><ul><li><a href="#banking-korea">3.1. Banking Transactions</a></li><li><a href="#video-service">3.2. Dr. What: Video Service</a></li><li><a href="#data-integrity">3.3. Code Sanctity and Bandwidth Saver</a></li><li><a href="#encrypt">3.4. Fostering Encrypted Communications</a></li><li><a href="#realtime-messaging">3.5. Off The Record Real Time Messaging</a></li><li><a href="#savemystuff">3.6. Documents In the Cloud</a></li></ul></li></ul></div>
</div>
<div id="sections">
@@ -324,20 +324,36 @@
[<a href="#digest">DIGEST</a> | <a href="#keycall">KEYCALL</a> | <a href="#verify">VERIFY</a>]</p>
</div>
<div id="encrypt" class="section">
- <h3>3.4. Mitch Turns 21: Encrypted Communications</h3>
- <p>Mark wishes to post pictures of Mitch's 21st birthday party to a social network that allows confidential and encrypted communication between members, but wishes to ensure that these pictures are safe from prying eyes -- more importantly, he wants them to be indecipherable digital data for everyone except Mitch. Mark can do the following: </p>
- <ol>
- <li><p>He can encrypt the photos with a key he generates for the occasion. [<a href="#derive">DERIVE</a> | <a href="#encrypt">ENCRYPT</a>]</p></li>
- <li><p>He can communicate with others on the network about the key and share the encrypted photos. [<a href="#keyex">KEYEX</a> | <a href="#encrypt-pki">ENCRYPT-PKI</a>] </p></li>
- <li><p>He can receive confidential communication from Mitch about the pictures via encrypted messages that are virtually impossible to read by any other entity than Mark. [<a href="#verify">VERIFY</a> | <a href="#decrypt-pki">DECRYPT-PKI</a>]</p></li>
- </ol>
+ <h3>3.4. Fostering Encrypted Communications</h3>
+ <p>Tantek wishes to communicate with Ryan securely. Moreover, Tantek wishes to use an email web application (EWA) provided by a third party, which is a web site that allows users who have accounts to set up email accounts of their own choosing -- that is, users can enter in existing POP/IMAP/SMTP username and password credentials, or simply use an email address provided by the EWA.</p>
+ <p>Ryan provides a PGP key on his website, encoded in the relevant conventions. For instance, he uses microformats where relevant, and follows the common practice of including a Base64 "blob" that represents his public key.</p>
+ <div class="example"><div class="exampleHeader">Example</div>
+ <p>Ryan uses the hCard format to encapsulate contact information with some semantic annotation within the markup of his webpage. Within the hCard, he does something like this:</p>
+ <div class="block"><div class="blockTitleDiv"><span class="blockTitle">ECMAScript</span></div><div class="blockContent"><pre class="code"><code class="es-code">
+
+<span class="key">
+-----BEGIN PGP PUBLIC KEY BLOCK-----
+Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
+Comment: GPGTools - http://gpgtools.org
+
+nQENBE4sjPMBCAC0ublKDnsdwD9B71bygmwVxn3hX6zw4H1Qlc6wPc0/OepjqVyq
+...
+-----END PGP PUBLIC KEY BLOCK-----
+</span>
+ </code></pre></div></div>
+<p>The ellipsis have been added for brevity.</p>
+ </div>
+<p>Logging on to EWA, Tantek may find UI that prompts him to enter in Ryan's hCard path. Tantek does so, and EWA then begins the process of importing Ryan's PGP key. In order to do so, it must first "scrub" the key format to be in one of the accepted import formats of the WebCrypto API.</p>
+<div class="example"><div class="exampleHeader">Example</div>
+<p>// TODO Enter sample code for importing public key.</p>
+</div>
</div>
<div id="realtime-messaging" class="section">
<h3>3.5. Off The Record Real Time Messaging</h3>
- <p>David and Nadim wish to have an "Off The Record" chat in real time, completely between them, and in text, including the ability to share digital data such as photographs. They log on to a chat server that serves up web content, and connect to each other's machines directly. The server merely serves up the chat client necessary, and does not log their conversation (and in fact cannot). David and Nadim need to:</p>
+ <p>David and Nadim wish to have an "Off The Record" chat in real time, completely between them, and in text, including the ability to share digital data such as photographs. They log on to a chat server, and connect to each other's machines directly. The server merely serves up the UI for the chat client, and does not log their conversation (and in fact, cannot). David and Nadim need to:</p>
<ul>
- <li><p>Be assured that they are who they claim they are. [<a href="#decrypt">DECRYPT</a> | <a href="#decrypt-pki">DECRYPT-PKI</a> | <a href="#encrypt">ENCRYPT</a> | <a href="#encrypt-pki">ENCRYPT-PKI</a>] </p></li>
- <li><p>Be assured that during a conversation, messages sent back and forth are unmodified. [<a href="#random">RANDOM</a> | <a href="#encrypt">ENCRYPT</a> | <a href="#decrypt">DECRYPT</a>] </p></li>
+ <li><p>Be assured that they are who they claim they are. [<a href="#sign">SIGN</a> | <a href="#verify">VERIFY</a> | <a href="#decrypt">DECRYPT</a> | <a href="#decrypt-pki">DECRYPT-PKI</a> | <a href="#encrypt">ENCRYPT</a> | <a href="#encrypt-pki">ENCRYPT-PKI</a>] </p></li>
+ <li><p>Be assured that during a conversation, messages sent back and forth are unmodified. [<a href="#encrypt">ENCRYPT</a> | <a href="#decrypt">DECRYPT</a>] </p></li>
<li><p>Be assured that after the conversation, the contents of the conversation cannot be determined. [???] </p></li>
</ul>