--- a/Overview-UseCases.xml Wed Dec 05 14:49:20 2012 -0500
+++ b/Overview-UseCases.xml Wed Dec 05 18:12:55 2012 -0500
@@ -130,8 +130,19 @@
<div id='banking-korea' class='section'>
<h3>Banking Transactions</h3>
<p>Park Jae-sang opens up a bank account with Gangnam Bank (GB), and wishes to log-in and engage in online transactions, including account balance checking, online payments (with some automated scheduled payments), and account transfers between domestic and investment accounts. The first time Park logs in to the GB website with a temporary verification code sent to his cell phone, the bank asks him to ascertain if the browser he is using is not at a kiosk; moreover, he is asked if it is a web browser and machine configuration he will use often.</p>
- <p>He confirms that it is. The GB web site then asks him to generate a public key/private key pair, along with a digital certificate. Park consents, and the web page creates the key pair, storing his private key in the browser's designated key store, along with a one-time key escrow by the bank. Jae-sang is also presented with a user guide that explains the validity period of the certificate, and for how long it will persist. [<a href="#derive">DERIVE</a> | <a href="#keyex-dh">KEYEX-DH</a>].</p>
- <p>Subsequent access to the GB website -- always over TLS -- is triggered via presentation of the key and certificate that Jae-sang generated when he first accessed the website. Along with a username and password, JavaScript initially loaded by GB contains a message that only Jae-sang can decipher, since it is encrypted with his public key. The message is deciphered, and the deciphered message is then digitally signed and sent back to the GB server. This establishes identity with non-repudiation. [<a href="#keycall">KEYCALL</a> | <a href="#decrypt-pki">DECRYPT-PKI</a> ].
+ <p>He confirms that it is. The GB web site then asks him to generate a public key/private key pair, along with a digital certificate. Park consents, and the web page creates the key pair, storing his private key in the browser's designated key store, along with a one-time key escrow by the bank. Additinoally, Jae-sang is presented with the bank's public key, such that documents issued by the bank can be verified and decrypted. Jae-sang is also presented with a user guide that explains the validity period of the certificate, and for how long it will persist. [<a href="#derive">DERIVE</a> | <a href="#keyex-dh">KEYEX-DH</a>].</p>
+ <div class="example">
+ <p>GB may first generate a key pair for Jae-sang. This is the public key/private key pair which will be used in subsequent transactions.</p>
+ <x:codeblock language="es">
+ <span class="comment">// TODO add derivation for ECDH </span>
+
+ </x:codeblock>
+ <p>GB may then use a key exchange mechanism to exchange keys with the server. This includes making sure that the client (Jae-sang) obtains a copy of GB's public key, and that GB obtains a copy of Jae-sang's public key. </p>
+ <x:codeblock>
+ <span class="comment">// TODO add DHKE code </span>
+ </x:codeblock>
+ </div>
+ <p>Subsequent access to the GB website -- always over TLS -- is triggered via presentation of the key and certificate that Jae-sang generated when he first accessed the website. JavaScript initially loaded by GB contains a message that only Jae-sang can decipher, since it is encrypted with his public key. The message is deciphered, and the deciphered message is then digitally signed and sent back to the GB server. This establishes identity with non-repudiation. [<a href="#keycall">KEYCALL</a> | <a href="#decrypt-pki">DECRYPT-PKI</a> ].
<div class="example">
<p><div class="ednote">Flesh out this example.</div> </p>
<x:codeblock language="es">
@@ -166,12 +177,12 @@
</x:codeblock>
</div>
- His browser presents this key every time he accesses the website and enters his password, which effectively binds his username and password to the generated private key and certificate. Additionally, Jae-sing can digitally sign online checks, authorize payments, and sign tax forms that he submits to the bank site using this generated key [<a href="#sign">SIGN</a>]. He can also perform the following tasks, following the authentication cycle describe above:</p>
+ His browser presents this key every time he accesses the website and enters his password, which effectively binds his username and password to the generated private key and certificate. Additionally, Jae-sang can digitally sign online checks, authorize payments, and sign tax forms that he submits to the bank site using this generated key [<a href="#sign">SIGN</a>]. He can also perform the following tasks, following the authentication cycle describe above:</p>
<ol>
- <li><p>Receive documents from GB via HTTP that only he can read. These include his private bank statements and tax documents. [<a href="#decrypt-pki">DECRYPT-PKI</a> | <a href="#decrypt">DECRYPT</a>]</p></li>
- <li><p>Submit documents to GB that only GB can read, with the assurance that these have come from Jae-sing. Such documents include confidential financial information. [<a href="#encrypt-pki">ENCRYPT-PKI</a>]</p></li>
+ <li><p>Receive documents from GB via HTTP that only he can read, with the assurance that they have come from GB and only GB. These include his private bank statements and tax documents, which are signed with his public key, already obtained in a previous step. [<a href="#decrypt-pki">DECRYPT-PKI</a> | <a href="#decrypt">DECRYPT</a>]</p></li>
+ <li><p>Submit documents to GB that only GB can read, with the assurance that these have come from Jae-sang. Such documents include confidential financial information. [<a href="#encrypt-pki">ENCRYPT-PKI</a>]</p></li>
</ol>
- <p>If GB wishes to "cache" aspects of reusuable authentication code, but cannot avail of a code signing system, GB can employ a similar data integrity mechanism that the <a href="#data-integrity">social networking site uses</a>.</p>
+ <p>If GB wishes to "cache" aspects of reusuable authentication code, but cannot avail of a code signing system, GB can employ a similar data integrity mechanism that the <a href="#data-integrity">social networking site uses</a>. Moreover, Jae-sang or GB may at any time reinitiate a key generation for subsequent transactions.</p>
</div>
<div id='video-service' class='section'>
<h3>Dr. What: Video Service</h3>
--- a/Overview.html Wed Dec 05 14:49:20 2012 -0500
+++ b/Overview.html Wed Dec 05 18:12:55 2012 -0500
@@ -146,8 +146,19 @@
<div id="banking-korea" class="section">
<h3>3.1. Banking Transactions</h3>
<p>Park Jae-sang opens up a bank account with Gangnam Bank (GB), and wishes to log-in and engage in online transactions, including account balance checking, online payments (with some automated scheduled payments), and account transfers between domestic and investment accounts. The first time Park logs in to the GB website with a temporary verification code sent to his cell phone, the bank asks him to ascertain if the browser he is using is not at a kiosk; moreover, he is asked if it is a web browser and machine configuration he will use often.</p>
- <p>He confirms that it is. The GB web site then asks him to generate a public key/private key pair, along with a digital certificate. Park consents, and the web page creates the key pair, storing his private key in the browser's designated key store, along with a one-time key escrow by the bank. Jae-sang is also presented with a user guide that explains the validity period of the certificate, and for how long it will persist. [<a href="#derive">DERIVE</a> | <a href="#keyex-dh">KEYEX-DH</a>].</p>
- <p>Subsequent access to the GB website -- always over TLS -- is triggered via presentation of the key and certificate that Jae-sang generated when he first accessed the website. Along with a username and password, JavaScript initially loaded by GB contains a message that only Jae-sang can decipher, since it is encrypted with his public key. The message is deciphered, and the deciphered message is then digitally signed and sent back to the GB server. This establishes identity with non-repudiation. [<a href="#keycall">KEYCALL</a> | <a href="#decrypt-pki">DECRYPT-PKI</a> ].
+ <p>He confirms that it is. The GB web site then asks him to generate a public key/private key pair, along with a digital certificate. Park consents, and the web page creates the key pair, storing his private key in the browser's designated key store, along with a one-time key escrow by the bank. Additinoally, Jae-sang is presented with the bank's public key, such that documents issued by the bank can be verified and decrypted. Jae-sang is also presented with a user guide that explains the validity period of the certificate, and for how long it will persist. [<a href="#derive">DERIVE</a> | <a href="#keyex-dh">KEYEX-DH</a>].</p>
+ <div class="example"><div class="exampleHeader">Example</div>
+ <p>GB may first generate a key pair for Jae-sang. This is the public key/private key pair which will be used in subsequent transactions.</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="comment">// TODO add derivation for ECDH </span>
+
+ </code></pre></div></div>
+ <p>GB may then use a key exchange mechanism to exchange keys with the server. This includes making sure that the client (Jae-sang) obtains a copy of GB's public key, and that GB obtains a copy of Jae-sang's public key. </p>
+ <div class="block"><div class="blockTitleDiv"><span class="blockTitle">@@</span></div><div class="blockContent"><pre class="code"><code class="-code">
+ <span class="comment">// TODO add DHKE code </span>
+ </code></pre></div></div>
+ </div>
+ <p>Subsequent access to the GB website -- always over TLS -- is triggered via presentation of the key and certificate that Jae-sang generated when he first accessed the website. JavaScript initially loaded by GB contains a message that only Jae-sang can decipher, since it is encrypted with his public key. The message is deciphered, and the deciphered message is then digitally signed and sent back to the GB server. This establishes identity with non-repudiation. [<a href="#keycall">KEYCALL</a> | <a href="#decrypt-pki">DECRYPT-PKI</a> ].
<div class="example"><div class="exampleHeader">Example</div>
<p><div class="ednote"><div class="ednoteHeader">Editorial note</div>Flesh out this example.</div> </p>
<div class="block"><div class="blockTitleDiv"><span class="blockTitle">ECMAScript</span></div><div class="blockContent"><pre class="code"><code class="es-code">
@@ -182,12 +193,12 @@
</code></pre></div></div>
</div>
- His browser presents this key every time he accesses the website and enters his password, which effectively binds his username and password to the generated private key and certificate. Additionally, Jae-sing can digitally sign online checks, authorize payments, and sign tax forms that he submits to the bank site using this generated key [<a href="#sign">SIGN</a>]. He can also perform the following tasks, following the authentication cycle describe above:</p>
+ His browser presents this key every time he accesses the website and enters his password, which effectively binds his username and password to the generated private key and certificate. Additionally, Jae-sang can digitally sign online checks, authorize payments, and sign tax forms that he submits to the bank site using this generated key [<a href="#sign">SIGN</a>]. He can also perform the following tasks, following the authentication cycle describe above:</p>
<ol>
- <li><p>Receive documents from GB via HTTP that only he can read. These include his private bank statements and tax documents. [<a href="#decrypt-pki">DECRYPT-PKI</a> | <a href="#decrypt">DECRYPT</a>]</p></li>
- <li><p>Submit documents to GB that only GB can read, with the assurance that these have come from Jae-sing. Such documents include confidential financial information. [<a href="#encrypt-pki">ENCRYPT-PKI</a>]</p></li>
+ <li><p>Receive documents from GB via HTTP that only he can read, with the assurance that they have come from GB and only GB. These include his private bank statements and tax documents, which are signed with his public key, already obtained in a previous step. [<a href="#decrypt-pki">DECRYPT-PKI</a> | <a href="#decrypt">DECRYPT</a>]</p></li>
+ <li><p>Submit documents to GB that only GB can read, with the assurance that these have come from Jae-sang. Such documents include confidential financial information. [<a href="#encrypt-pki">ENCRYPT-PKI</a>]</p></li>
</ol>
- <p>If GB wishes to "cache" aspects of reusuable authentication code, but cannot avail of a code signing system, GB can employ a similar data integrity mechanism that the <a href="#data-integrity">social networking site uses</a>.</p>
+ <p>If GB wishes to "cache" aspects of reusuable authentication code, but cannot avail of a code signing system, GB can employ a similar data integrity mechanism that the <a href="#data-integrity">social networking site uses</a>. Moreover, Jae-sang or GB may at any time reinitiate a key generation for subsequent transactions.</p>
</div>
<div id="video-service" class="section">
<h3>3.2. Dr. What: Video Service</h3>