BSD Ports

www/threema-web 2.5.5 DragonFly

Threema Web application

System
DragonFly
Repository
DPorts
Maintainer
[email protected] (as in FreeBSD)
License
AGPLv3
Categories
net-im, www
Package size
22335.0 KiB, 29912.4 KiB installed

Description

Threema's web client allows you to use Threema on the desktop without compromising security.

* Complete synchronization: By scanning a QR code, desktop and mobile device are connected at once, and all conversations are fully accessible on the desktop.

* Security and data restraint: All communication between phone and PC is fully end-to-end encrypted. After the session is terminated, all synchronized messages are immediately deleted in the browser.

* Open Source: Threema Web is open source and uses open standards. It is also possible to host Threema Web on your own server.

In the other systems

The newest version among them is 2.6.2, as upstream numbers it.

SystemPortVersionVulnerabilitiesStatusMaintainerLast update
DragonFlywww/threema-web2.5.5none known-[email protected]-
FreeBSDwww/threema-web2.6.2 newestnone known-[email protected]-
HardenedBSDwww/threema-web2.6.2 newestno data-[email protected]-
GhostBSDwww/threema-web2.6.2 newestno data-[email protected]-

Install

Binary package:

pkg install threema-web

From DPorts:

cd /usr/dports/www/threema-web && make install clean

Dependencies

No port depends on this one.

Configuration

No options to configure.

Service scripts
none

Message after installing

This is Threema Web, compiled with 'SELF_HOSTED=true' and with pre-defined
  STUN/TURN and SaltyRTC servers on its bundled configuration. If you want to run
  your own servers you must recompile this port yourself and make sure to define
  the following variables:

    THREEMA_ICE_CREDEN, the credentials for "threema-angular" (static username);
    THREEMA_ICE_SERVER, your STUN server in a "hostname:port" format; 
    THREEMA_SALTYRTC_HOST, your SaltyRTC server;
    THREEMA_SALTYRTC_PORT, the port of your SaltyRTC server,
    THREEMA_SALTYRTC_KEY, the key used by your SaltyRTC server.

  The web server needs to set the proper MIME type for *.wasm (WebAssembly) files.

  If you use nginx, this would go into nginx's mime types:

    application/wasm wasm;

  Should you opt for Apache, then you would need to add this to httpd.conf:

    AddType application/wasm .wasm

  Make sure to serve Threema Web only via HTTPS. It's also recommend to enable
  HSTS, HPKP, CSP and other available security mechanisms in your web server.

  If you deployed it to be used on a server with restrictive CSP rules, make sure
  to add "static.threema.ch" as an allowed style/font source.

  NOTE: While you could in theory host your own version of the "push-server",
        it won't help much since the GCM/APN API Keys required to dispatch push
        notifications to the Threema app are *NOT* public.