Feature #7690

Host our internal XMPP chatroom on Tails infrastructure

Added by intrigeri 2014-07-30 14:56:45 . Updated 2019-03-24 16:00:17 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Start date:
2014-07-30
Due date:
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

We have to move our internal XMPP chatroom out of the server where it currently lives.

Subtasks

Related issues

Related to Tails - Feature #7874: Find a more stable solution for Tails default chat support channel Resolved 2015-10-28

History

#1 Updated by mukul 2014-12-26 05:37:41

intrigeri wrote:
h2. > We have to move our internal XMPP chatroom out of the server where it currently lives.

I do have a spare server, on which a tails http mirror is also being hosted.

#2 Updated by intrigeri 2014-12-28 08:57:55

> I do have a spare server, on which a tails http mirror is also being hosted.

Thanks for the offer! Just to be clear: we have the hardware. Next step is to choose what XMPP server software we’ll use (likely prosody or ejabberd), and look for existing Puppet modules able to set up and manage them on Debian stable or Jessie.

#3 Updated by intrigeri 2015-03-20 21:57:11

  • related to Feature #7874: Find a more stable solution for Tails default chat support channel added

#4 Updated by intrigeri 2015-03-21 01:45:18

Puppet modules to manage a XMPP server:

  • mayflower/prosody : 1y old, 5 releases; seems well-maintained and up-to-date wrt. current best practices
  • JohannDickson/prosody : very recent, no idea how long it’ll be maintained; installs prosody from upstream’s APT repo
  • buzzdeee/ejabberd : only 2 releases, no idea how long it’ll be maintained; no doc whatsoever; relatively well-written; pretends to support only OpenBSD, but I’ve not found anything OpenBSD-specific in its codebase
  • lboynton/ejabberd : 1y old, 5 releases; relatively well-written; might share some code or history with buzzdeee/ejabberd

#5 Updated by sajolida 2015-03-21 14:55:25

Ticket Feature #7874 mentions “requirements” specified on this ticket to be able to choose the right XMPP server. I only see in this ticket the implicit need for a maintained puppet module.

Anything else?

#6 Updated by intrigeri 2015-03-21 15:37:31

> Ticket Feature #7874 mentions “requirements” specified on this ticket

On Feature #7874, when I wrote “the ticket”, I meant Feature #7874, not Feature #7690. Sorry for being unclear.

(I bet there two things are orthogonal, that’s why I tried to keep the two discussions separate: I doubt we trust any existing public XMPP server to host our internal chatroom, and I doubt we’ll want to host a public XMPP server ourselves for user support.)

#7 Updated by intrigeri 2015-04-05 18:04:50

  • Status changed from Confirmed to In Progress
  • Assignee set to intrigeri
  • % Done changed from 0 to 10

I’ve set up a im.lizard VM. Next step is to choose between prosody and ejabberd, possibly using the research I’ve done two weeks ago about Puppet modules to manage them.

#9 Updated by intrigeri 2016-09-02 03:51:38

  • Status changed from In Progress to Rejected
  • Assignee deleted (intrigeri)

I’m giving up on that one, and hope that our current hosting setup will work better in the future. bertagaz, feel free to reopen + take it if you want.

#10 Updated by intrigeri 2017-07-25 09:33:22

  • Status changed from Rejected to Confirmed
  • Assignee set to intrigeri
  • Target version set to Tails_3.3

Reopening as we now have a working internal XMPP server.

#11 Updated by intrigeri 2017-07-29 16:27:01

  • Status changed from Confirmed to Rejected
  • Assignee deleted (intrigeri)
  • Target version deleted (Tails_3.3)

Will reopen only if/when this internal server supports ACLs so we can allow only team members to access their team’s chan.

#12 Updated by intrigeri 2019-03-24 15:44:47

  • Status changed from Rejected to Confirmed

intrigeri wrote:
> Will reopen only if/when this internal server supports ACLs so we can allow only team members to access their team’s chan.

Actually, that’s already possible. One needs to be the MUC owner (which is the case when one has just created it) and then use /config to make the room members-only, then /affiliate to add members.

I’m a bit fed up that our internal XMPP chatroom is so often unavailable so I’m going to migrate it to im.lizard, where tails-bar already lives.

#13 Updated by intrigeri 2019-03-24 16:00:17

  • Status changed from Confirmed to Resolved
  • % Done changed from 10 to 100

Done!