Databases
StackOverflow2013
Postsdbo
POClient-side encryption over HTTP with Diffie-Hellman Key Exchange and AES
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POClient-side encryption over HTTP with Diffie-Hellman Key Exchange and AES
    primarykey
    data
    text
    <p>After watching a YouTube video on the <a href="http://www.youtube.com/watch?v=3QnD2c4Xovk">Diffie-Hellman Key Exchange</a>, I wanted to try an implementation in JavaScript (Atwood's law).</p> <p>I sketched up an cipher on Node.js with the following rules:</p> <ul> <li><p>Step 1: Client and server agree on a shared key:</p> <ul> <li><p>Client &amp; server start with a 512bit prime public key pK</p></li> <li><p>Client generates a 512bit prime private key kC and sends powMod(3, kC, pK)</p></li> <li><p>Server generates a 512bit prime private key kS and sends powMod(3, kS, pK)</p></li> <li><p>Client &amp; Server use powMod(response, privatekey, pK) as the shared key</p></li> </ul></li> <li><p>Step 2: Communication</p> <ul> <li><p>Before a client sends data it is encrypted with the shared key using the Stanford Javascript Crypto Library (256bit AES, HMAC authentication, PBKDF2 password strengthening, and CCM authenticated-encryption.)</p></li> <li><p>Once the server decrypts the data with the shared key, it generates a new 512bit prime private key and sends it as a SJCL encrypted response.</p></li> <li><p>The client and server switch to a new shared key using powMod(3, prevSharedKey, newPrivKey)</p></li> </ul></li> </ul> <p>Now I have a few questions..</p> <p>How secure would such a system be in comparison with HTTPS or other algorithms? What are the weakest points of such a system?</p> <p>In terms of security / practicality, would it be better to use 1024 bit keys for stronger security? Are the HMAC/PBKDF2/CCM options overkill? Is it worth modulating the shared key? Thanks for reading!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USarby
    1. USarby
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POClient-side encryption over HTTP with Diffie-Hellman Key Exchange and AES
      1. USamar
      1. VTFavorite
    2. VO
      singulars
      1. POClient-side encryption over HTTP with Diffie-Hellman Key Exchange and AES
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POClient-side encryption over HTTP with Diffie-Hellman Key Exchange and AES
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload