CI to automate build of webrtc tarball for signal-desktop aport https://gitlab.alpinelinux.org/alpine/aports/-/tree/master/testing/signal-desktop
Find a file
2014-06-01 13:39:35 -04:00
css Thread model and UI improvements 2014-05-26 15:33:45 -07:00
js Retry API, standardize <script> list 2014-06-01 13:39:35 -04:00
js-deps Backbone message storage and views 2014-05-17 20:26:50 -07:00
pnacl Regenerate bins for fixed ephemeral bit 2014-05-04 02:21:31 -04:00
protos New protos with group messaging stuff 2014-03-12 12:54:39 -07:00
background.html Retry API, standardize <script> list 2014-06-01 13:39:35 -04:00
curve25519-donna-wrapper.cpp LGPL license (I'd like to be an axolotl/TS JS lib in the future) 2014-05-04 02:34:13 -04:00
curve25519-donna.c I like stack traces, also, fix identity key bit fiddle crap 2014-05-04 02:21:31 -04:00
curve25519-donna.h Updates, NaCL 2014-01-22 06:23:41 +00:00
GPL LGPL license (I'd like to be an axolotl/TS JS lib in the future) 2014-05-04 02:34:13 -04:00
icon.png Random things from James-Firth incl update icon 2014-05-26 00:55:38 +02:00
LGPL LGPL license (I'd like to be an axolotl/TS JS lib in the future) 2014-05-04 02:34:13 -04:00
Makefile Updates, NaCL 2014-01-22 06:23:41 +00:00
manifest.json Updates, NaCL 2014-01-22 06:23:41 +00:00
options.css LGPL license (I'd like to be an axolotl/TS JS lib in the future) 2014-05-04 02:34:13 -04:00
options.html Retry API, standardize <script> list 2014-06-01 13:39:35 -04:00
popup.html Retry API, standardize <script> list 2014-06-01 13:39:35 -04:00
README.md Random things from James-Firth incl update icon 2014-05-26 00:55:38 +02:00
test.html Retry API, standardize <script> list 2014-06-01 13:39:35 -04:00

TextSecure Chromium Implementation

This is very early stuff and exists primarily to get the crypto in place. It is currently chromium-only as it uses NaCL for Curve25519 stuff, but I'd be glad to accept a pull that abstracts out the NaCL-specific stuff to optionally use a JS implementation for FF. Note that the code is currently quite messy (its all in one file!), but it needs to work first, then it can be heavily cleaned up later.

Getting Started with Development

  • Clone the repo
  • Open Chrome
  • Go to chrome://extensions/
  • Enable developer mode (checkbox on the top right)
  • Click "Load unpacked extension..."
  • Point to the repo's directory

Tips/Tricks

  • For Dev purposes, the test server always uses code 111111