Bump version to 0.13.13

[signal-cli] / README.md

diff --git a/README.md b/README.md
index 093b0eef52efa6da09bc966fa38f066fea614fd8..e6d6e5ff7d8815d1ff23f605be25e941a749151f 100644 (file)
--- a/README.md
+++ b/README.md
@@ -3,13 +3,18 @@
 signal-cli is a commandline interface for the [Signal messenger](https://signal.org/).
 It supports registering, verifying, sending and receiving messages.
 signal-cli uses a [patched libsignal-service-java](https://github.com/Turasa/libsignal-service-java),
 signal-cli is a commandline interface for the [Signal messenger](https://signal.org/).
 It supports registering, verifying, sending and receiving messages.
 signal-cli uses a [patched libsignal-service-java](https://github.com/Turasa/libsignal-service-java),

-extracted from the [Signal-Android source code](https://github.com/signalapp/Signal-Android/tree/main/libsignal/service).
+extracted from the [Signal-Android source code](https://github.com/signalapp/Signal-Android/tree/main/libsignal-service).

 For registering you need a phone number where you can receive SMS or incoming calls.
 
 For registering you need a phone number where you can receive SMS or incoming calls.
 

-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)).
+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 JSON-RPC interface ([man page](https://github.com/AsamK/signal-cli/blob/master/man/signal-cli-jsonrpc.5.adoc))
+and D-BUS interface ([man page](https://github.com/AsamK/signal-cli/blob/master/man/signal-cli-dbus.5.adoc)) .

 For the JSON-RPC interface there's also a simple [example client](https://github.com/AsamK/signal-cli/tree/master/client), written in Rust.
 
 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 needs to be kept up-to-date to keep up with Signal-Server changes.
+The official Signal clients expire after three months and then the Signal-Server can make incompatible changes.
+So signal-cli releases older than three months may not work correctly.
+

 ## Installation
 
 You can [build signal-cli](#building) yourself or use
 ## Installation
 
 You can [build signal-cli](#building) yourself or use


@@ -18,7 +23,7 @@ Windows. There's also a [docker image and some Linux packages](https://github.co
 
 System requirements:
 
 
 System requirements:
 

-- at least Java Runtime Environment (JRE) 17
+- at least Java Runtime Environment (JRE) 21

 - native library: libsignal-client
 
   The native libs are bundled for x86_64 Linux (with recent enough glibc), Windows and MacOS. For other
 - native library: libsignal-client
 
   The native libs are bundled for x86_64 Linux (with recent enough glibc), Windows and MacOS. For other


@@ -31,15 +36,14 @@ See [latest version](https://github.com/AsamK/signal-cli/releases).
 
 ```sh
 export VERSION=<latest version, format "x.y.z">
 
 ```sh
 export VERSION=<latest version, format "x.y.z">

-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
+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/
 ```
 
 You can find further instructions on the Wiki:
 
 - [Quickstart](https://github.com/AsamK/signal-cli/wiki/Quickstart)
 sudo ln -sf /opt/signal-cli-"${VERSION}"/bin/signal-cli /usr/local/bin/
 ```
 
 You can find further instructions on the Wiki:
 
 - [Quickstart](https://github.com/AsamK/signal-cli/wiki/Quickstart)

-- [DBus Service](https://github.com/AsamK/signal-cli/wiki/DBus-service)

 
 ## Usage
 
 
 ## Usage
 


@@ -53,10 +57,17 @@ of all country codes.)
 
 * Register a number (with SMS verification)
 
 
 * Register a number (with SMS verification)
 

-        signal-cli -a ACCOUNT register
+      signal-cli -a ACCOUNT register
+
+  You can register Signal using a landline number. In this case, you need to follow the procedure below:
+   * Attempt a SMS verification process first (`signal-cli -a ACCOUNT register`)
+     * You will get an error `400 (InvalidTransportModeException)`, this is normal
+   * Wait 60 seconds
+   * Attempt a voice call verification by adding the `--voice` switch and wait for the call:

 
 

-  You can register Signal using a landline 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.
+     ```sh
+     signal-cli -a ACCOUNT register --voice
+     ```

 
   Registering may require solving a CAPTCHA
   challenge: [Registration with captcha](https://github.com/AsamK/signal-cli/wiki/Registration-with-captcha)
 
   Registering may require solving a CAPTCHA
   challenge: [Registration with captcha](https://github.com/AsamK/signal-cli/wiki/Registration-with-captcha)


@@ -64,19 +75,21 @@ of all country codes.)
 * 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
 
 * 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 -a ACCOUNT verify CODE
+      signal-cli -a ACCOUNT verify CODE

 
 * Send a message
 
 
 * Send a message
 

-        signal-cli -a ACCOUNT send -m "This is a message" RECIPIENT
+     ```sh
+     signal-cli -a ACCOUNT send -m "This is a message" RECIPIENT
+     ```

 
 * Pipe the message content from another process.
 
 
 * Pipe the message content from another process.
 

-        uname -a | signal-cli -a ACCOUNT send --message-from-stdin RECIPIENT
+      uname -a | signal-cli -a ACCOUNT send --message-from-stdin RECIPIENT

 
 * Receive messages
 
 
 * Receive messages
 

-        signal-cli -a ACCOUNT receive
+      signal-cli -a ACCOUNT receive

 
 **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
 
 **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


@@ -86,8 +99,8 @@ and other features.
 
 The password and cryptographic keys are created when registering and stored in the current users home directory:
 
 
 The password and cryptographic keys are created when registering and stored in the current users home directory:
 

-        $XDG_DATA_HOME/signal-cli/data/
-        $HOME/.local/share/signal-cli/data/
+    $XDG_DATA_HOME/signal-cli/data/
+    $HOME/.local/share/signal-cli/data/

 
 ## Building
 
 
 ## Building
 


@@ -96,44 +109,45 @@ version installed, you can replace `./gradlew` with `gradle` in the following st
 
 1. Checkout the source somewhere on your filesystem with
 
 
 1. Checkout the source somewhere on your filesystem with
 

-        git clone https://github.com/AsamK/signal-cli.git
+       git clone https://github.com/AsamK/signal-cli.git

 
 2. Execute Gradle:
 
 
 2. Execute Gradle:
 

-        ./gradlew build
+       ./gradlew build

 
    2a. Create shell wrapper in *build/install/signal-cli/bin*:
 
 
    2a. Create shell wrapper in *build/install/signal-cli/bin*:
 

-        ./gradlew installDist
+       ./gradlew installDist

 
    2b. Create tar file in *build/distributions*:
 
 
    2b. Create tar file in *build/distributions*:
 

-        ./gradlew distTar
+       ./gradlew distTar

 
    2c. Create a fat tar file in *build/libs/signal-cli-fat*:
 
 
    2c. Create a fat tar file in *build/libs/signal-cli-fat*:
 

-        ./gradlew fatJar
+       ./gradlew fatJar

 
    2d. Compile and run signal-cli:
 
 
    2d. Compile and run signal-cli:
 

-        ./gradlew run --args="--help"
+      ```sh
+      ./gradlew run --args="--help"
+      ```

 
 ### Building a native binary with GraalVM (EXPERIMENTAL)
 
 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.
 
 
 ### Building a native binary with GraalVM (EXPERIMENTAL)
 
 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.
 

-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:
+1. [Install GraalVM and setup the environment](https://www.graalvm.org/docs/getting-started/#install-graalvm)
+2. Execute Gradle:

 
 

-        ./gradlew nativeCompile
+       ./gradlew nativeCompile

 
    The binary is available at *build/native/nativeCompile/signal-cli*
 
 ## FAQ and Troubleshooting
 
 
    The binary is available at *build/native/nativeCompile/signal-cli*
 
 ## FAQ and Troubleshooting
 

-For frequently asked questions and issues have a look at the [wiki](https://github.com/AsamK/signal-cli/wiki/FAQ)
+For frequently asked questions and issues have a look at the [wiki](https://github.com/AsamK/signal-cli/wiki/FAQ).

 
 ## License
 
 
 ## License