Implementation of the olm and megolm cryptographic ratchets
Find a file
2017-01-04 11:46:37 +01:00
docs Add a document on signing keys 2016-10-27 11:55:48 +01:00
fuzzers Fix broken fuzzer compilation 2016-10-24 16:32:21 +01:00
include/olm Document the return values for olm_matches_inbound_session 2016-10-25 14:42:10 +01:00
java/android/OlmLibSdk OlmAccount methods trigger an exception when they fail. 2017-01-04 11:46:37 +01:00
javascript Version bump for 2.0.0 2016-10-25 11:35:20 +01:00
lib Fix Ed25519 keypair generation 2016-09-01 13:35:23 +01:00
python Update python wrapper to run against libolm.so.2 2016-10-25 14:50:15 +01:00
src Return the base64-encoded length of pickles 2016-10-24 10:06:06 +01:00
tests Document the return values for olm_matches_inbound_session 2016-10-25 14:42:10 +01:00
tracing switch from /usr/bin/python to /usr/bin/env python. this doesn't help folks whose python path points at python3 (e.g. Arch linux) though, but I see no choice than they have to change the shebangs, as we do on Synapse. For instance, OSX doesn't have a python2 symlink, otherwise we'd use /usr/bin/env python2 shebang. 2015-11-01 13:05:51 +00:00
.gitignore Add a document on signing keys 2016-10-27 11:55:48 +01:00
CHANGELOG.rst Changelog: Mention install-headers 2016-10-24 17:22:43 +01:00
jenkins.sh Fix jenkins.sh 2016-09-16 17:34:21 +01:00
LICENSE Copyright notices and a license 2015-02-26 16:56:25 +00:00
Makefile Add a document on signing keys 2016-10-27 11:55:48 +01:00
README.rst Update the README files. 2017-01-02 14:04:53 +01:00
version_script.ver Use a version script to restrict symbols in the .so 2016-05-20 15:15:40 +01:00

Olm
===

An implementation of the Double Ratchet cryptographic ratchet described by
https://github.com/trevp/double_ratchet/wiki, written in C and C++11 and
exposed as a C API.

The specification of the Olm ratchet can be found in ``docs/olm.rst`` or
https://matrix.org/docs/spec/olm.html.

This library also includes an implementation of the Megolm cryptographic
ratchet, as specified in ``docs/megolm.rst`` or
https://matrix.org/docs/spec/megolm.html.

Building
--------

To build olm as a shared library run:

.. code:: bash

    make

To run the tests run:

.. code:: bash

    make test

To build the javascript bindings, install emscripten from http://kripken.github.io/emscripten-site/ and then run:

.. code:: bash

    make js
	
To build the android project for Android bindings, run:

	.. code:: bash
	cd java/android/OlmLibSdk
	./gradlew clean assembleRelease

Release process
---------------

.. code:: bash

    # Bump version numbers in ``Makefile`` and ``javascript/package.json``
    # Prepare changelog
    git commit
    make clean
    make test
    make js
    npm pack javascript
    VERSION=x.y.z
    scp olm-$VERSION.tgz packages@ldc-prd-matrix-001:/sites/matrix/packages/npm/olm/
    git tag $VERSION -s
    git push --tags

It's probably sensible to do the above on a release branch (``release-vx.y.z``
by convention), and merge back to master once complete.


Design
------

Olm is designed to be easy port to different platforms and to be easy
to write bindings for.

It was originally implemented in C++, with a plain-C layer providing the public
API. As development has progressed, it has become clear that C++ gives little
advantage, and new functionality is being added in C, with C++ parts being
rewritten as the need ariases.

Error Handling
~~~~~~~~~~~~~~

All C functions in the API for olm return ``olm_error()`` on error.
This makes it easy to check for error conditions within the language bindings.

Random Numbers
~~~~~~~~~~~~~~

Olm doesn't generate random numbers itself. Instead the caller must
provide the random data. This makes it easier to port the library to different
platforms since the caller can use whatever cryptographic random number
generator their platform provides.

Memory
~~~~~~

Olm avoids calling malloc or allocating memory on the heap itself.
Instead the library calculates how much memory will be needed to hold the
output and the caller supplies a buffer of the appropriate size.

Output Encoding
~~~~~~~~~~~~~~~

Binary output is encoded as base64 so that languages that prefer unicode
strings will find it easier to handle the output.

Dependencies
~~~~~~~~~~~~

Olm uses pure C implementations of the cryptographic primitives used by
the ratchet. While this decreases the performance it makes it much easier
to compile the library for different architectures.

What's an olm?
--------------

It's a really cool species of European troglodytic salamander.
http://www.postojnska-jama.eu/en/come-and-visit-us/vivarium-proteus/

Legal Notice
------------

The software may be subject to the U.S. export control laws and regulations
and by downloading the software the user certifies that he/she/it is
authorized to do so in accordance with those export control laws and
regulations.