X-Git-Url: https://git.nmode.ca/signal-cli/blobdiff_plain/bc17f9317e09c97907123da06a44b42b67f16b0d..9da2a0040358c57c27fbbf3c98d416b243070832:/README.md diff --git a/README.md b/README.md index cc9bde5f..50442c34 100644 --- a/README.md +++ b/README.md @@ -1,155 +1,140 @@ # signal-cli -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. To be able to receiving messages signal-cli uses a [patched libsignal-service-java](https://github.com/AsamK/libsignal-service-java), because libsignal-service-java [does not yet support registering for the websocket support](https://github.com/WhisperSystems/libsignal-service-java/pull/5) nor [provisioning as a slave device](https://github.com/WhisperSystems/libsignal-service-java/pull/21). For registering you need a phone number where you can receive SMS or incoming calls. -It is primarily intended to be used on servers to notify admins of important events. For this use-case, it has a dbus interface, that can be used to send messages from any programming language that has dbus bindings. +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. 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 linked device](https://github.com/WhisperSystems/libsignal-service-java/pull/21). For +registering you need a phone number where you can receive SMS or incoming calls. -## Installation - -You can [build signal-cli](#building) yourself, or use the provided binary files, 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/). You need to have at least JRE 7 installed, to run signal-cli. - -### Install system-wide on Linux -```sh -export VERSION= -wget https://github.com/AsamK/signal-cli/releases/download/v"${VERSION}"/signal-cli-"${VERSION}".tar.gz -sudo tar xf signal-cli-"${VERSION}".tar.gz -C /opt -sudo ln -sf /opt/signal-cli-"${VERSION}"/bin/signal-cli /usr/local/bin/ -``` - -## Usage - -usage: signal-cli [-h] [-v] [--config CONFIG] [-u USERNAME | --dbus | --dbus-system] {link,addDevice,listDevices,removeDevice,register,verify,send,quitGroup,updateGroup,receive,daemon} ... - -* Register a number (with SMS verification) +signal-cli is primarily intended to be used on servers to notify admins of important events. For this use-case, it has a daemon mode with D-BUS +interface ([man page](https://github.com/AsamK/signal-cli/blob/master/man/signal-cli-dbus.5.adoc)) and JSON-RPC interface ([documentation](https://github.com/AsamK/signal-cli/wiki/JSON-RPC-service)). For the JSON-RPC interface there's also a simple [example client](https://github.com/AsamK/signal-cli/tree/master/client), written in Rust. - signal-cli -u USERNAME register - -* Register a number (with voice verification) - - signal-cli -u USERNAME register -v - -* Verify the number using the code received via SMS or voice - - signal-cli -u USERNAME verify CODE - -* Send a message to one or more recipients +## Installation - signal-cli -u USERNAME send -m "This is a message" [RECIPIENT [RECIPIENT ...]] [-a [ATTACHMENT [ATTACHMENT ...]]] +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. There's also a [docker image and some Linux packages](https://github.com/AsamK/signal-cli/wiki/Binary-distributions) provided by the community. -* Pipe the message content from another process. +System requirements: - uname -a | signal-cli -u USERNAME send [RECIPIENT [RECIPIENT ...]] - -* Receive messages +- at least Java Runtime Environment (JRE) 17 +- native library: libsignal-client - signal-cli -u USERNAME receive + The native libs are bundled for x86_64 Linux (with recent enough glibc), Windows and MacOS. For other + systems/architectures + see: [Provide native lib for libsignal](https://github.com/AsamK/signal-cli/wiki/Provide-native-lib-for-libsignal) -* Groups +### Install system-wide on Linux - * Create a group +See [latest version](https://github.com/AsamK/signal-cli/releases). - signal-cli -u USERNAME updateGroup -n "Group name" -m [MEMBER [MEMBER ...]] +```sh +export VERSION= +wget https://github.com/AsamK/signal-cli/releases/download/v"${VERSION}"/signal-cli-"${VERSION}"-Linux.tar.gz +sudo tar xf signal-cli-"${VERSION}"-Linux.tar.gz -C /opt +sudo ln -sf /opt/signal-cli-"${VERSION}"/bin/signal-cli /usr/local/bin/ +``` - * Update a group +You can find further instructions on the Wiki: - signal-cli -u USERNAME updateGroup -g GROUP_ID -n "New group name" -a "AVATAR_IMAGE_FILE" +- [Quickstart](https://github.com/AsamK/signal-cli/wiki/Quickstart) +- [DBus Service](https://github.com/AsamK/signal-cli/wiki/DBus-service) - * Add member to a group +## Usage - signal-cli -u USERNAME updateGroup -g GROUP_ID -m "NEW_MEMBER" +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). - * Leave a group +Important: The ACCOUNT 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.) - signal-cli -u USERNAME quitGroup -g GROUP_ID +* Register a number (with SMS verification) - * Send a message to a group + signal-cli -a ACCOUNT register - signal-cli -u USERNAME send -m "This is a message" -g GROUP_ID + 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. -* Linking other devices (Provisioning) + Registering may require solving a CAPTCHA + challenge: [Registration with captcha](https://github.com/AsamK/signal-cli/wiki/Registration-with-captcha) - * Connect to another device +* 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 - signal-cli link -n "optional device name" - - This shows a "tsdevice:/…" link, if you want to connect to another signal-cli instance, you can just use this link. If you want to link to and Android device, create a QR code with the link (e.g. with [qrencode](https://fukuchi.org/works/qrencode/)) and scan that in the Signal Android app. + signal-cli -a ACCOUNT verify CODE - * Add another device +* Send a message - signal-cli -u USERNAME addDevice --uri "tsdevice:/…" - - The "tsdevice:/…" link is the one shown by the new signal-cli instance or contained in the QR code shown in Signal-Desktop or similar apps. - Only the master device (that was registered directly, not linked) can add new devices. + signal-cli -a ACCOUNT send -m "This is a message" RECIPIENT - * Manage linked devices +* Pipe the message content from another process. - signal-cli -u USERNAME listDevices + uname -a | signal-cli -a ACCOUNT send --message-from-stdin RECIPIENT - signal-cli -u USERNAME removeDevice -d DEVICE_ID +* Receive messages -## DBus service + signal-cli -a ACCOUNT receive -signal-cli can run in daemon mode and provides an experimental dbus interface. -For dbus support you need jni/unix-java.so installed on your system (Debian: libunixsocket-java ArchLinux: libmatthew-unix-java (AUR)). +**Hint**: The Signal protocol expects that incoming messages are regularly received (using `daemon` or `receive` +command). This is required for the encryption to work efficiently and for getting updates to groups, expiration timer +and other features. -* Run in daemon mode (dbus session bus) +## Storage - signal-cli -u USERNAME daemon +The password and cryptographic keys are created when registering and stored in the current users home directory: -* Send a message via dbus + $XDG_DATA_HOME/signal-cli/data/ + $HOME/.local/share/signal-cli/data/ - signal-cli --dbus send -m "Message" [RECIPIENT [RECIPIENT ...]] [-a [ATTACHMENT [ATTACHMENT ...]]] +## Building -### System bus +This project uses [Gradle](http://gradle.org) for building and maintaining dependencies. If you have a recent gradle +version installed, you can replace `./gradlew` with `gradle` in the following steps. -To run on the system bus you need to take some additional steps. -It’s advisable to run signal-cli as a separate unix user, the following steps assume you created a user named *signal-cli*. -These steps, executed as root, should work on all distributions using systemd. +1. Checkout the source somewhere on your filesystem with -```bash -cp data/org.asamk.Signal.conf /etc/dbus-1/system.d/ -cp data/org.asamk.Signal.service /usr/share/dbus-1/system-services/ -cp data/signal.service /etc/systemd/system/ -sed -i -e "s|%dir%||" -e "s|%number%||" /etc/systemd/system/signal.service -systemctl daemon-reload -systemctl enable signal.service -systemctl reload dbus.service -``` + git clone https://github.com/AsamK/signal-cli.git -Then just execute the send command from above, the service will be autostarted by dbus the first time it is requested. +2. Execute Gradle: -## Storage + ./gradlew build -The password and cryptographic keys are created when registering and stored in the current users home directory: + 2a. Create shell wrapper in *build/install/signal-cli/bin*: - $HOME/.config/signal/data/ + ./gradlew installDist -For legacy users, the old config directory is used as a fallback: + 2b. Create tar file in *build/distributions*: - $HOME/.config/textsecure/data/ + ./gradlew distTar -## Building + 2c. Create a fat tar file in *build/libs/signal-cli-fat*: -This project uses [Gradle](http://gradle.org) for building and maintaining -dependencies. If you have a recent gradle version installed, you can replace `./gradlew` with `gradle` in the following steps. + ./gradlew fatJar -1. Checkout the source somewhere on your filesystem with + 2d. Compile and run signal-cli: - git clone https://github.com/AsamK/signal-cli.git + ./gradlew run --args="--help" -2. Execute Gradle: +### Building a native binary with GraalVM (EXPERIMENTAL) - ./gradlew build +It is possible to build a native binary with [GraalVM](https://www.graalvm.org). This is still experimental and will not +work in all situations. -3. Create shell wrapper in *build/install/signal-cli/bin*: +1. [Install GraalVM and setup the enviroment](https://www.graalvm.org/docs/getting-started/#install-graalvm) +2. [Install prerequisites](https://www.graalvm.org/reference-manual/native-image/#prerequisites) +3. Execute Gradle: - ./gradlew installDist + ./gradlew nativeCompile -4. Create tar file in *build/distributions*: + The binary is available at *build/native/nativeCompile/signal-cli* - ./gradlew distTar +## FAQ and Troubleshooting -## Troubleshooting -If you use a version of the Oracle JRE and get an InvalidKeyException you need to enable unlimited strength crypto. See https://stackoverflow.com/questions/6481627/java-security-illegal-key-size-or-default-parameters for instructions. +For frequently asked questions and issues have a look at the [wiki](https://github.com/AsamK/signal-cli/wiki/FAQ) ## License