You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Lennart Grahl eae0c5d0fb
Various clarifications and cleanup (#156)
6 months ago
media Media files (#91) 3 years ago
.editorconfig Re-wrap all paragraphs 3 years ago
.gitignore Add .gitignore file 2 years ago Chunking 1.1: Split into reliable/ordered mode and unreliable/unordered mode (#153) 8 months ago
LICENSE Bump date 2 years ago Reword accepting of client messages (#139) 8 months ago Add 'saltyrtc-server-go' implementation link to readme (#151) 10 months ago Fix PGP key URL (#129) 2 years ago Relayed Data Task (#141) 1 year ago All tasks must support application messages (#144) 1 year ago Various clarifications and cleanup (#156) 6 months ago


Join our chat on Gitter

SaltyRTC is an end-to-end encrypted signalling protocol. It offers to freely choose from a range of signalling tasks, such as setting up a WebRTC or ORTC peer-to-peer connection, or simply to exchange arbitrary data over the established transport in a secure manner. SaltyRTC is completely open to new and custom signalling tasks for everything feasible.

In this repository, you can find…


If you have implemented a SaltyRTC client, task or server :+1: and you would like to add it to this list, we will gladly accept a pull request from you.

Clients and Tasks



When we release a new version of the protocol, a (new) task or the chunking specification, a tag will be added in the following format: protocol|chunking-<version> or for tasks task-<task-name>-<version>.

Note that specification versions are independent from each other. In case a new version of a specification breaks backwards compatibility to another specification, it will include a section stating how compatibility is affected.