Project

General

Profile

Bug #14504

Investigate mobile messaging platforms

Added by spriver 3 months ago. Updated about 1 month ago.

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
08/30/2017
Due date:
% Done:

0%

QA Check:
Feature Branch:
Type of work:
Research

Description

As discussed at the summit we should investigate several mobile messaging platforms.
Following characteristics should be considered:
  • availability of end-to-end encryption
  • availability and types of desktop clients
  • mass adoption
  • etc.

Team: anonym, spriver, (segfault)

History

#1 Updated by spriver 3 months ago

  • Description updated (diff)

#2 Updated by spriver 3 months ago

  • Blueprint changed from https://tails.boum.org/blueprint/mobile_messaging to https://tails.boum.org/blueprint/mobile_messaging/

#3 Updated by spriver 3 months ago

  • Assignee set to spriver

#4 Updated by intrigeri 3 months ago

  • Target version changed from 2018 to 2019

(as per updated roadmap)

#5 Updated by sajolida about 2 months ago

Today I tried the desktop version of Telegram on Debian over Tor and it worked like a charm!

See https://tracker.debian.org/pkg/telegram-desktop

You can configure Tor as a SOCKS5 proxy in the configuration. The traffic seems to go through HTTP.

When first starting the app, you have to enter your phone number and validate it through an SMS. Then you get all your messages and conversations back, even your stickers!

So it's not anonymous in the sense that it's linked with your phone number but it's super easy :)

I bet it works fine with Tails. It could be documented once we have Additional Software.

#6 Updated by spriver about 2 months ago

sajolida wrote:

Today I tried the desktop version of Telegram on Debian over Tor and it worked like a charm!

See https://tracker.debian.org/pkg/telegram-desktop

You can configure Tor as a SOCKS5 proxy in the configuration. The traffic seems to go through HTTP.

When first starting the app, you have to enter your phone number and validate it through an SMS. Then you get all your messages and conversations back, even your stickers!

So it's not anonymous in the sense that it's linked with your phone number but it's super easy :)

I bet it works fine with Tails. It could be documented once we have Additional Software.

I started working on this topic in the last days (gathered and started to read some whitepapers, etc.) and also stumbled upon Telegram in Debian (: It also works inside of Tails (after configuring the SOCKS proxy inside of Telegram). There's also a working icon in the top bar. I did not test it to configure it persistently, but it's maybe possible as the config, data etc. is stored in ~/.local/share/TelegramDesktop/. I'll test it more in the next days as I'm using Telegram (confession time (; ) on a daily basis and I'd be super happy to have it working well integrated into Tails.

#7 Updated by spriver about 1 month ago

Signal (https://signal.org/) announced that the until now used Chromium-based desktop application is deprecated, it's going to be replaced by a (Electron framework [https://electron.atom.io/] based) standalone application, thus dropping the requirement of installing Chromium to use Signal Messenger on a Desktop system.

So far the application is available in the repo of Signal, I don't know if it's going to be available via the Debian native repositories someday.

Edit after some brief testing (in Tails):

  • adding the repo is only possible when apt-transport-https is installed, the repo is refusing plain HTTP connections
  • the executable is huge:
    Need to get 97.3 MB of archives.
    After this operation, 226 MB of additional disk space will be used.
  • starting the app is no problem, but it's not possible to configure a proxy. the app won't boot at all when it's started via torsocks in CLI -> AFAICT the application is (atm) not usable in Tails. The issue tracker of signal-desktop has an open ticket wrt. adding SOCKS proxy support (https://github.com/WhisperSystems/Signal-Desktop/issues/1430)
  • settings/data are stored in ~/.config/Signal/

Also available in: Atom PDF