Quick blog post I worked on a few days ago and finally got released:
So electron improved their security features with the recent version 5, but by doing this broke tons of applications because they either need User Namespaces or an SUID executeable (to launch proper isolated subprocesses).
#Signal Desktop noticed this problem and as well and "fixed" it in the worst way possible:
On the other hand #Riot Desktop did a proper fix, which enables an SUID bit on this binary: https://github.com/vector-im/riot-web/commit/56674ea70849b3a793fa7b862945163aa10b36b8
Riot v1.1.1 is on its way to your desktop 🎉
The Flatpak was updated. Just waiting for the build to finish and publishing to flathub.
When Gnome Software is configured properly on your system, you'll just get a notification that Riot was updated in Background as soon as it made it to your system 🚀
For everyone else: Run `flatpak update` tomorrow and it should wait for you to install 🙂
There are new keys for the official matrix repositories with the key ids:
Those come along with a new package that are build on fresh infrastructure. No details if they now sign packages offline, yet.
Since Matrix reset all logins recently, you may lost some of your E2EE keys. Those were erased when being forcefully logged out.
Those who used the Key Backup mechanism by Matrix.org can recover quite easily, those who didn't bother to set them up, might have a problem.
In #e2e:matrix.org we discussed that today and someone provided a detailed guide on how to recover using BTRFS:
Matrix.org just announced they are back once more:
Let's hope things stay up as they are. There are definitely some new challenges to tackle, which came up in their issue tracker:
Let's see if they got really rid of the attacker 🤞
Too early to be happy, seems like the attacker found their way in and is still around on Matrix's infrastructure.
The attack has proven themselves to have shell access on their synapse instance, which is definitely bad. It means that all user accounts are compromised and have to be reset.
There will go a lot of efforts into figuring out the details and fixing the vulnerability.
Meanwhile, send some love to the people behind matrix!
Matrix is coming back up! One of the first things happening was writing a new blog post about the incident which you can find here:
TL;DR: Some outdated software was discovered and cracked by an attack which then had access to various data points.
Important: Change your password ASAP (including NickServ when you used the IRC bridges)
Hint: The homeserver is not back up yet.
Seems like Matrix.org is getting ready to come back!
If you wonder where the CodiMD community channel went, here is a short text explaining it:
TL;DR: Matrix.org is rebuilding their infrastructure from scratch after a security incident.
@matrix Turns out that there was a successful compromise of the Matrix infrastructure happening.
Details from Matrix on Twitter: https://twitter.com/matrixdotorg/status/1116388572922302466
You may ask how that could happen, but more important: It didn't stay unnoticed and that's a good sign.
For those who run on Matrix.org and wonder why there is no connection:
Matrix announced an emergency maintenance… on Twitter:
Sadly @matrix didn't receive the love it deserves and informs the Fediverse.
Anyway, that's why we have a community. We compensate short coming of each other and together make sure the world becomes a better place!
Right now we only allow write access to the Downloads directory, which causes problem with drag and drop and sending files in general. We currently considering to give access to the entire home directory, but the big question is: Allow writing or read-only access?
Discussion can be found here:
If someone is into CPP or electron development, please have a look at:
I'm a professional relationship therapist for programs and their users.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!