1. 31 Mar, 2021 1 commit
  2. 06 Oct, 2020 1 commit
  3. 01 Oct, 2020 1 commit
  4. 26 Sep, 2020 1 commit
  5. 19 May, 2020 1 commit
  6. 16 May, 2020 1 commit
  7. 15 May, 2020 1 commit
  8. 07 May, 2020 1 commit
  9. 30 Sep, 2019 1 commit
  10. 08 Aug, 2019 1 commit
  11. 30 Jan, 2019 1 commit
  12. 22 Jan, 2019 1 commit
  13. 05 Oct, 2018 1 commit
  14. 04 Oct, 2018 1 commit
  15. 03 Oct, 2018 1 commit
  16. 25 Sep, 2018 1 commit
    • David Baker's avatar
      Another day, another interface · 263b9442
      David Baker authored
      Change the interface again, hopefully this time a bit more normal.
      Now we wrap the emscripten module completely and just expose the
      high level objects.
      
      The olm library export is now imported as normal (ie. returns
      a module rather than a function returning a module) but has an
      `init` method which *must* be called. This returns a promise
      which resolves when the module is ready. It also rejects if the
      module failed to set up, unlike before (and unlike the
      promise-not-a-promise that emscripten returns).
      
      Generally catch failures to init the module.
      263b9442
  17. 21 Sep, 2018 2 commits
    • David Baker's avatar
      Make OLM_OPTIONS work again · 5e87db61
      David Baker authored
      The closure compiler was just renaming the variable so it never
      would have picked them up. Make it an extern so it knows what to do.
      5e87db61
    • David Baker's avatar
      WebAssembly support! · 122867c4
      David Baker authored
      Quite a lot going on in this PR:
       * Updates to support recent emscripten, switching to WASM which is now the default
       * Use emscripten's MODULARIZE option rather than wrapping it ourself, since doing
         so in pre-post js doesn't work anymore.
       * Most changes are moving the emscripten runtime functions to top-level
         calls rather than in the Module object.
       * Get rid of duplicated NULL_BYTE_PADDING_LENGTH
       * Fix ciphertext_length used without being declared
       * Fix things that caused the closure compiler to error, eg. using
         OLM_OPTIONS without a declaration.
       * Wait until module is inited to do OLM_ERROR = olm_error()
      
      The main BREAKING CHANGE here is that the module now needs to initialise
      asyncronously (because it has to load the wasm file). require()ing olm
      now gives a function which needs to be called to create an instance.
      The resulting object has a promise-like then() method that can be used
      to detect when the module is ready. (We could use MODULARIZE_INSTANCE
      to return the module directly as before, rather than the function,
      but then we don't get the .then() method).
      122867c4
  18. 18 Jul, 2018 1 commit
  19. 27 Jun, 2018 1 commit
  20. 12 Apr, 2018 1 commit
  21. 29 Mar, 2017 1 commit
  22. 24 Mar, 2017 1 commit
  23. 02 Mar, 2017 1 commit
  24. 01 Mar, 2017 1 commit
  25. 18 Jan, 2017 2 commits
  26. 22 Dec, 2016 1 commit
  27. 17 Nov, 2016 1 commit
  28. 27 Oct, 2016 1 commit
  29. 25 Oct, 2016 1 commit
  30. 23 Sep, 2016 2 commits
  31. 22 Sep, 2016 1 commit
  32. 14 Sep, 2016 1 commit
  33. 06 Sep, 2016 1 commit
  34. 05 Sep, 2016 1 commit
  35. 01 Sep, 2016 1 commit
    • Richard van der Hoff's avatar
      Fix Ed25519 keypair generation · 0c462cff
      Richard van der Hoff authored
      Ed25519 private keys, it turns out, have 64 bytes, not 32.
      
      We were previously generating only 32 bytes (which is all that is required to
      generate the public key), and then using the public key as the upper 32 bytes
      when generating the per-message session key. This meant that everything
      appeared to work, but the security of the private key was severely compromised.
      
      By way of fixes:
      
       * Use the correct algorithm for generating the Ed25519 private key, and store
         all 512 bits of it.
      
       * Update the account pickle format and refuse to load the old format (since we
         should consider it compromised).
      
       * Bump the library version, and add a function to retrieve the library
         version, so that applications can verify that they are linked against a
         fixed version of the library.
      
       * Remove the curve25519_{sign, verify} functions which were unused and of
         dubious quality.
      0c462cff
  36. 11 Jul, 2016 2 commits