Meet.coop update October 2025

[kawaiipunk]

@chris

Have you asked Komubit to root the ca.meet.coop server for you? This should be a straight forward matter of them shutting it down and appending your SSH public keys to /root/.ssh/authorized_keys and checking that /etc/ssh/sshd_config allows logins with keys and then restarting it?

Yep we are doing that now. We have been able to recover the FDE password for it so should be fine.

[anarcat]

@kawaiipunk

Yep we are doing that now. We have been able to recover the FDE password for it so should be fine.

sorry for doing this ping thing, but any update here?

[flancian]

Hi all! Thank you very much for your welcome and for your continued work on these topics

@kawaiipunk: I’m unsure what FDE access means in this context, sorry; have we found a way forward towards getting “Keycloak sso.meet.coop master realm access”? Social.coop members are currently still unable to log in and are pinging about this.

If not, should we set a timeline to give up on previous auth and recreate Social.coop users in the new SSO domain/setup? This would probably unblock some of our users which depend on BBB features but can let go on previous rooms/recordings.

Thank you!

[kawaiipunk]

Hi @flancian to restate that non technically, me and Nick are unable to make much progress on this due to the fact that we don’t have the access we need to do it.

We’re meeting up tomorrow to try and work out next steps.

[anarcat]

@flancian

I’m unsure what FDE access means in this context

for what it’s worth, I believe FDE here means “full disk encryption”, and above, we mean “we found the key to decrypt the disks”.

[kawaiipunk]

Hi folks,

As you may has seen, we have been making faster progress.

We are close to bringing into production, the new Dockerised Keycloak server that is supported and easy to upgrade going forwards.

We have also pressed ahead with the restore recordings plan after a vote that was carried out.

After these two tasks are completed, we are in an excellent position and we can get rid of the old and servers that are full of technical baggage. It’s been quite the journey! This process should set us for the next five years of operation with secure maintained infrastructure.