nmode's Git Repositories - signal-cli/blob - README.md

   1 # signal-cli
   2
   3 signal-cli is a commandline interface for [libsignal-service-java](https://github.com/WhisperSystems/libsignal-service-java). It supports registering, verifying, sending and receiving messages.
   4 To be able to link to an existing Signal-Android/signal-cli instance, signal-cli uses a [patched libsignal-service-java](https://github.com/AsamK/libsignal-service-java), because libsignal-service-java does not yet support [provisioning as a slave device](https://github.com/WhisperSystems/libsignal-service-java/pull/21).
   5 For registering you need a phone number where you can receive SMS or incoming calls.
   6 signal-cli is primarily intended to be used on servers to notify admins of important events. For this use-case, it has a dbus interface ([man page](https://github.com/AsamK/signal-cli/blob/master/man/signal-cli-dbus.5.adoc)), that can be used to send messages from any programming language that has dbus bindings.
   7
   8 ## Installation
   9
  10 You can [build signal-cli](#building) yourself, or use the [provided binary files](https://github.com/AsamK/signal-cli/releases/latest), which should work on Linux, macOS and Windows. For Arch Linux there is also a [package in AUR](https://aur.archlinux.org/packages/signal-cli/) and there is a [FreeBSD port](https://www.freshports.org/net-im/signal-cli) available as well.
  11
  12 System requirements:
  13 - at least Java Runtime Environment (JRE) 11
  14 - native libraries: libzkgroup, libsignal-client
  15
  16   Those are bundled for x86_64 Linux, for other systems/architectures see: [Provide native lib for libsignal](https://github.com/AsamK/signal-cli/wiki/Provide-native-lib-for-libsignal)
  17
  18 ### Install system-wide on Linux
  19 See [latest version](https://github.com/AsamK/signal-cli/releases).
  20 ```sh
  21 export VERSION=<latest version, format "x.y.z">
  22 wget https://github.com/AsamK/signal-cli/releases/download/v"${VERSION}"/signal-cli-"${VERSION}".tar.gz
  23 sudo tar xf signal-cli-"${VERSION}".tar.gz -C /opt
  24 sudo ln -sf /opt/signal-cli-"${VERSION}"/bin/signal-cli /usr/local/bin/
  25 ```
  26 You can find further instructions on the Wiki:
  27 - [Quickstart](https://github.com/AsamK/signal-cli/wiki/Quickstart)
  28 - [DBus Service](https://github.com/AsamK/signal-cli/wiki/DBus-service)
  29
  30 ## Usage
  31
  32 For a complete usage overview please read the [man page](https://github.com/AsamK/signal-cli/blob/master/man/signal-cli.1.adoc) and the [wiki](https://github.com/AsamK/signal-cli/wiki).
  33
  34 Important: The USERNAME is your phone number in international format and must include the country calling code. Hence it should start with a "+" sign. (See [Wikipedia](https://en.wikipedia.org/wiki/List_of_country_calling_codes) for a list of all country codes.)
  35
  36 * Register a number (with SMS verification)
  37
  38         signal-cli -u USERNAME register
  39
  40   You can register Signal using a land line number. In this case you can skip SMS verification process and jump directly to the voice call verification by adding the `--voice` switch at the end of above register command.
  41
  42   Registering may require solving a CAPTCHA challenge: [Registration with captcha](https://github.com/AsamK/signal-cli/wiki/Registration-with-captcha)
  43
  44 * Verify the number using the code received via SMS or voice, optionally add `--pin PIN_CODE` if you've added a pin code to your account
  45
  46         signal-cli -u USERNAME verify CODE
  47
  48 * Send a message
  49
  50         signal-cli -u USERNAME send -m "This is a message" RECIPIENT
  51
  52 * Pipe the message content from another process.
  53
  54         uname -a | signal-cli -u USERNAME send RECIPIENT
  55
  56 * Receive messages
  57
  58         signal-cli -u USERNAME receive
  59
  60
  61 ## Storage
  62
  63 The password and cryptographic keys are created when registering and stored in the current users home directory:
  64
  65 `$XDG_DATA_HOME/signal-cli/data/` (`$HOME/.local/share/signal-cli/data/`)
  66
  67 For legacy users, the old config directories are used as a fallback:
  68
  69         $HOME/.config/signal/data/
  70
  71         $HOME/.config/textsecure/data/
  72
  73 ## Building
  74
  75 This project uses [Gradle](http://gradle.org) for building and maintaining
  76 dependencies. If you have a recent gradle version installed, you can replace `./gradlew` with `gradle` in the following steps.
  77
  78 1. Checkout the source somewhere on your filesystem with
  79
  80         git clone https://github.com/AsamK/signal-cli.git
  81
  82 2. Execute Gradle:
  83
  84         ./gradlew build
  85
  86 3. Create shell wrapper in *build/install/signal-cli/bin*:
  87
  88         ./gradlew installDist
  89
  90 4. Create tar file in *build/distributions*:
  91
  92         ./gradlew distTar
  93
  94 ### Building a native binary with GraalVM (EXPERIMENTAL)
  95
  96 It is possible to build a native binary with [GraalVM](https://www.graalvm.org).
  97 This is still experimental and will not work in all situations.
  98
  99 1. [Install GraalVM and setup the enviroment](https://www.graalvm.org/docs/getting-started/#install-graalvm)
 100 2. [Install prerequisites](https://www.graalvm.org/reference-manual/native-image/#prerequisites)
 101 3. Execute Gradle:
 102
 103         ./gradlew assembleNativeImage
 104
 105    The binary is available at *build/native-image/signal-cli*
 106
 107 ## FAQ and Troubleshooting
 108 For frequently asked questions and issues have a look at the [wiki](https://github.com/AsamK/signal-cli/wiki/FAQ)
 109
 110 ## License
 111
 112 This project uses libsignal-service-java from Open Whisper Systems:
 113
 114 https://github.com/WhisperSystems/libsignal-service-java
 115
 116 Licensed under the GPLv3: http://www.gnu.org/licenses/gpl-3.0.html