Cwtch messaging

[Patrick]

This could use some documentation to be written:
https://www.whonix.org/wiki/Chat#Cwtch

@nyxnor

Add Cwtch profile by nyxnor · Pull Request #8 · Whonix/onion-grater · GitHub

Any git changes are in the stable repository for a while now.

[Patrick]

@storms

I’m not sure whether this is expected behaviour, but even after “Reload Firewall”, the Whonix User Firewall Settings File /etc/whonix_firewall.d/50_user.conf still appears empty. The Whonix docs imply that it would not be empty if a change to the firewall settings was made.

If it’s empty then you didn’t make a change to the firewall configuration file.

The upstream documentation is terse but mentions, quote:

The Whonix-Workstation Firewall needs to have the possible Cwtch binding port open. Follow the upstream firewall guide.

But it seems to me that many users ignore links, take it as optional, don’t click it. Without that it can be indeed hard to edit that file.

[Patrick]

@nyxnor

#713 - Detect Whonix to simplify launch - cwtch-ui - Open Privacy Gitea

Unfortunately upstream replied won't fix.

[Patrick]

Debian request for packaging:
RFP: cwtch – Privacy Preserving Infrastructure for Asynchronous, Decentralized, Multi-Party, and Metadata Resistant Applications

[Patrick]

Cwtch upstream feature request:

digital software signatures - sign releases

[Patrick]

@Patrick

@nyxnor

#713 - Detect Whonix to simplify launch - cwtch-ui - Open Privacy Gitea

Unfortunately upstream replied won't fix.

But that’s a non-issue because there’s a install-whonix.sh script provided by upstream.

[Patrick]

@Patrick

This could use some documentation to be written:
Instant Messenger Chat

Documentation now exists. Testers welcome.

---

remaining imperfections:

• startup command /home/user/.local/bin/cwtch is a bit cumbersome
• The install-whonix.sh by default installs to the home folder. In the future this will cause a conflict with Enhanced Security via Mount Options and Compiler Restrictions. This would be a non-issue if installed to the system. That would happen if a .deb was available.

---

A .deb is planned, mentioned in a comment here by upstream:

Add distribution via Flatpak

[mimp]

Tested the instructions. It works for me.

[storms]

There is a response on this issue regarding reproducibility vs. signing.

[Patrick]

I cannot answer the question

@adrelanos Is the fact that Cwtch is reproducible on Debian sufficient for it to be included in Whonix?

on the Cwtch issue tracker for ticket #802 - digital software signatures - sign releases - cwtch-ui - Open Privacy Gitea. Discussion of Whonix Default Application Policy seems off-topic.

Just because I opened the ticket under my name, doesn’t mean it’s Whonix specific. The ticket should stand or fall irrespective of Whonix.

The decision to implement or reject the ticket is for upstream alone.

[storms]

There is now a deb package, as of 1.15, see release notes

Is that sufficient for Cwtch to be included as default software in Whonix?

[Patrick]

Not planned.

[nurmagoz]

@Patrick

Unfortunately upstream replied won't fix.

Hmm thats not great…