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-10-26 21:27:08 -07:00
css Refactor options page and style using bootstrap 2014-10-14 13:59:43 -07:00
images with love from tyler 2014-07-27 11:36:03 -10:00
js Remove unused *MACWithVersionByte functions 2014-10-26 21:27:08 -07:00
js-deps Avoid background thread overwriting outgoing messages 2014-10-15 19:01:30 -07:00
nacl JS ed25519 2014-07-20 16:49:40 -04:00
protos Fix a missing function and dont blow up on delivery receipts 2014-07-26 01:53:24 -04:00
stylesheets render attachments 2014-10-26 00:30:20 -07:00
test Fixes #61 - Order by timestamps with tests 2014-10-20 02:07:46 -07:00
background.html Refactor textsecure.protos -> textsecure.protobuf 2014-10-20 15:11:16 -07:00
icon.png Random things from James-Firth incl update icon 2014-05-26 00:55:38 +02:00
index.html render attachments 2014-10-26 00:30:20 -07: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
manifest.json use new index page for popup 2014-08-25 19:01:18 -07:00
options.html Refactor textsecure.protos -> textsecure.protobuf 2014-10-20 15:11:16 -07:00
popup.html Fix message sending 2014-07-27 11:35:49 -10:00
README.md Add some initial development setup instructions. 2014-10-17 20:37:35 -04:00
test.html Refactor textsecure.protos -> textsecure.protobuf 2014-10-20 15:11:16 -07:00
X11 rm useless GPL, license testvectors under X11 (ie 3-c MIT + advertising provision) 2014-10-26 02:59:59 -07:00

TextSecure Chromium Implementation

This is very early stuff and exists primarily to get the crypto in place. This does not currently work, dont bother trying to use it seriously yet

Getting Started with Development

These steps are for development only.

  • 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

Note that for development, the TextSecure staging environment uses a self-signed certificate, which Chrome will complain is insecure. So first visit https://textsecure-service-staging.whispersystems.org/ in your browser and allow the certificate.

Now, in the extension's options, you can register for TextSecure:

  • Select "Register" under "I'm new to TextSecure".
  • Enter a real phone number (Google Voice numbers work too) and country combination and choose to send an SMS. You will receive a real SMS.
  • Enter the verification code you received by SMS.

You should now be able to use the extension. If you need to reset your development environment, open a browser console within the extension options page (or inspect background.html) and execute localStorage.clear() to clear out the settings.

Tests

Please write tests! Our testing framework is mocha and our assertion library is chai:

Tips/Tricks

  • Loading the test.html page may read, write or clear localStorage. To avoid having to choose between running tests and preserving your existing messages, keys, and other extension data, much of the test suite can be run by starting a local webserver in the repository root, e.g. python -m SimpleHTTPServer. You can then access the test page at http://0.0.0.0:8000/test.html.