From 41864d46c314942a6e1fb82b82f69636a29fa763 Mon Sep 17 00:00:00 2001 From: Richard van der Hoff Date: Thu, 1 Jun 2017 13:04:04 +0100 Subject: [PATCH] Load Olm from the global rather than requiring it. This means that we can avoid confusing everybody in the world about how to webpack js-sdk apps. --- README.md | 18 ++++++++++++++++++ package.json | 9 +-------- src/client.js | 3 +-- src/crypto/OlmDevice.js | 6 ++---- 4 files changed, 22 insertions(+), 14 deletions(-) diff --git a/README.md b/README.md index c51ca5b2d..5c549062b 100644 --- a/README.md +++ b/README.md @@ -236,6 +236,24 @@ host the API reference from the source files like this: Then visit ``http://localhost:8005`` to see the API docs. +End-to-end encryption support +============================= + +The SDK supports end-to-end encryption via the Olm and Megolm protocols, using +[libolm](http://matrix.org/git/olm). It is left up to the application to make +libolm available, via the ``Olm`` global. + +To enable support in a browser application: + + * download the transpiled libolm (either via ``npm install olm``, or from + https://matrix.org/packages/npm/olm/). + * load ``olm.js`` as a ``