Tails

#2 Updated by goupille 2018-01-22 00:18:34

I gave a try to Wire in tails 3.4 :

There is a debian package (https://wire-app.wire.com/linux/debian/pool/main/wire_3.0.2816_amd64.deb) “However, it is an experimental build and we expect to see some issues in day-to-day usage. We don’t offer official support at the moment, but any issues can be reported via ”$“:https://github.com/wireapp/wire-desktop”
their repo is only accessible with https, the package is 51Mb and depends on gconf2-common libappindicator1 libdbusmenu-glib4 libdbusmenu-gtk libgconf-2-4 libindicator7 (After this operation, 7,685 kB of additional disk space will be used.)

I started wire-desktop —proxy-server=“socks5://localhost:9050” in a terminal (starting it through Applications>Internet>Wire didn’t work, there is no way to configure the proxy in the GUI)

you can then create an account with a phone number OR with an email address (a verification code is sent in both cases), and the settings seems to be stored in ~/.config/Wire/

I was able to send and receive text messages.
I was also able to receive VOIP calls, but I wasn’t able to initiate a call (apparently wire tries to talk to the gateway on the local network) :

[5629:0122/000322.890145:ERROR:stunport.cc(88)] Binding request timed out from 192.168.122.x:48881 (eth0)

I didn’t try video calls.

#4 Updated by Anonymous 2018-01-22 16:47:16

goupille wrote:
> I gave a try to Wire in tails 3.4 :

<3!

> I was also able to receive VOIP calls, but I wasn’t able to initiate a call (apparently wire tries to talk to the gateway on the local network).

For this problem we should try to see if it works in Debian / if this was a firewall issue?

#5 Updated by goupille 2018-02-03 16:29:27

> For this problem we should try to see if it works in Debian / if this was a firewall issue?

I tried on a debian sid and a debian stretch, on both, ferm was stopped and wire-desktop used tor with the option above, and voice call are working well.
when ferm is started with the default configuration there are no issues either, it is only my firewall rules (and those of tails) that prevent wire to ‘get out’.

I can’t test video calls since I don’t have webcams.

#6 Updated by goupille 2018-02-03 17:22:14

note that for some “multi-device usability”, Wire is keeping (apparently unencrypted) the list of your contacts on their server until you delete your account : https://motherboard.vice.com/en_us/article/secure-messaging-app-wire-stores-everyone-youve-ever-contacted-in-plain-text

the key is attached to a device, not to the account, and it is not easy to verify (I mean, there is no “verify” button, I had to search a little to find the fingerprint of my contact).

#7 Updated by Anonymous 2018-02-04 09:45:47

goupille wrote:
> note that for some “multi-device usability”, Wire is keeping (apparently unencrypted) the list of your contacts on their server until you delete your account : https://motherboard.vice.com/en_us/article/secure-messaging-app-wire-stores-everyone-youve-ever-contacted-in-plain-text
>
> the key is attached to a device, not to the account, and it is not easy to verify (I mean, there is no “verify” button, I had to search a little to find the fingerprint of my contact).

Thanks for reporting back! I will add this info to the blueprint https://tails.boum.org/blueprint/mobile_messaging/!

#8 Updated by mercedes508 2018-02-21 16:20:42

> their repo is only accessible with https, the package is 51Mb and depends on gconf2-common libappindicator1 libdbusmenu-glib4 libdbusmenu-gtk libgconf-2-4 libindicator7 (After this operation, 7,685 kB of additional disk space will be used.)

I’m trying it right now in Tails 3.5, and it needs libdbusmenu-gtk4 and not libdbusmenu-gtk.

#9 Updated by goupille 2018-02-22 10:35:01

it seems wire use UDP for the VOIP part, so that won’t work :

https://support.wire.com/hc/en-us/articles/115005341805-What-domain-names-and-ports-does-Wire-connect-to-