]> nmode's Git Repositories - signal-cli/blob - README.md
256445bf41eafcf7760cac1cc27b0fe76ef8743d
[signal-cli] / 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. 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.
4 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.
5
6 ## Usage
7
8 usage: signal-cli [-h] [-v] [--config CONFIG] [-u USERNAME | --dbus | --dbus-system] {link,addDevice,listDevices,removeDevice,register,verify,send,quitGroup,updateGroup,receive,daemon} ...
9
10 * Register a number (with SMS verification)
11
12 signal-cli -u USERNAME register
13
14 * Register a number (with voice verification)
15
16 signal-cli -u USERNAME register -v
17
18 * Verify the number using the code received via SMS or voice
19
20 signal-cli -u USERNAME verify CODE
21
22 * Send a message to one or more recipients
23
24 signal-cli -u USERNAME send -m "This is a message" [RECIPIENT [RECIPIENT ...]] [-a [ATTACHMENT [ATTACHMENT ...]]]
25
26 * Pipe the message content from another process.
27
28 uname -a | signal-cli -u USERNAME send [RECIPIENT [RECIPIENT ...]]
29
30 * Receive messages
31
32 signal-cli -u USERNAME receive
33
34 * Groups
35
36 * Create a group
37
38 signal-cli -u USERNAME updateGroup -n "Group name" -m [MEMBER [MEMBER ...]]
39
40 * Update a group
41
42 signal-cli -u USERNAME updateGroup -g GROUP_ID -n "New group name" -a "AVATAR_IMAGE_FILE"
43
44 * Add member to a group
45
46 signal-cli -u USERNAME updateGroup -g GROUP_ID -m "NEW_MEMBER"
47
48 * Leave a group
49
50 signal-cli -u USERNAME quitGroup -g GROUP_ID
51
52 * Send a message to a group
53
54 signal-cli -u USERNAME send -m "This is a message" -g GROUP_ID
55
56 * Linking other devices (Provisioning)
57
58 * Connect to another device
59
60 signal-cli link -n "optional device name"
61
62 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.
63
64 * Add another device
65
66 signal-cli -u USERNAME addDevice --uri "tsdevice:/…"
67
68 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.
69 Only the master device (that was registered directly, not linked) can add new devices.
70
71 * Manage linked devices
72
73 signal-cli -u USERNAME listDevices
74
75 signal-cli -u USERNAME removeDevice -d DEVICE_ID
76
77 ## DBus service
78
79 signal-cli can run in daemon mode and provides an experimental dbus interface.
80 For dbus support you need jni/unix-java.so installed on your system (Debian: libunixsocket-java ArchLinux: libmatthew-unix-java (AUR)).
81
82 * Run in daemon mode (dbus session bus)
83
84 signal-cli -u USERNAME daemon
85
86 * Send a message via dbus
87
88 signal-cli --dbus send -m "Message" [RECIPIENT [RECIPIENT ...]] [-a [ATTACHMENT [ATTACHMENT ...]]]
89
90 ### System bus
91
92 To run on the system bus you need to take some additional steps.
93 It’s advisable to run signal-cli as a separate unix user, the following steps assume you created a user named *signal-cli*.
94 These steps, executed as root, should work on all distributions using systemd.
95
96 ```bash
97 cp data/org.asamk.Signal.conf /etc/dbus-1/system.d/
98 cp data/org.asamk.Signal.service /usr/share/dbus-1/system-services/
99 cp data/signal.service /etc/systemd/system/
100 sed -i -e "s|%dir%|<INSERT_INSTALL_PATH>|" -e "s|%number%|<INSERT_YOUR_NUMBER>|" /etc/systemd/system/signal.service
101 systemctl daemon-reload
102 systemctl enable signal.service
103 systemctl reload dbus.service
104 ```
105
106 Then just execute the send command from above, the service will be autostarted by dbus the first time it is requested.
107
108 ## Storage
109
110 The password and cryptographic keys are created when registering and stored in the current users home directory:
111
112 $HOME/.config/signal/data/
113
114 For legacy users, the old config directory is used as a fallback:
115
116 $HOME/.config/textsecure/data/
117
118 ## Building
119
120 This project uses [Gradle](http://gradle.org) for building and maintaining
121 dependencies. If you have a recent gradle version installed, you can replace `./gradlew` with `gradle` in the following steps.
122
123 1. Checkout the source somewhere on your filesystem with
124
125 git clone https://github.com/AsamK/signal-cli.git
126
127 2. Execute Gradle:
128
129 ./gradlew build
130
131 3. Create shell wrapper in *build/install/signal-cli/bin*:
132
133 ./gradlew installDist
134
135 4. Create tar file in *build/distributions*:
136
137 ./gradlew distTar
138
139 ## Troubleshooting
140 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.
141
142 ## License
143
144 This project uses libsignal-service-java from Open Whisper Systems:
145
146 https://github.com/WhisperSystems/libsignal-service-java
147
148 Licensed under the GPLv3: http://www.gnu.org/licenses/gpl-3.0.html