By the way, there was an update for Riot yesterday.

When you use Gnome Software and have automatic updates for flatpaks activated, it's very likely you have it already installed.

Otherwise, go for it :)

For CLI users: `flatpak update` will do the job.

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

By the way, the Riot 1.1.0 flatpak is on its way

Just wait for the repository metadata to be updates and things will arrive on your workstation :)

There are new keys for the official matrix repositories with the key ids:
CF45A512DE2DA058 (synapse)
D7B0B66941D01538 (riot)

Those come along with a new package that are build on fresh infrastructure. No details if they now sign packages offline, yet.

twitter.com/matrixdotorg/statu

twitter.com/RiotChat/status/11

Updated my OpenPGP-signed Riot verification keys, now that I run an own homeserver.

shivering-isles.com/riot-signe

Just if you want to verify me without me being around :)

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 :matrix.org we discussed that today and someone provided a detailed guide on how to recover using BTRFS:

matrix.to/#/!boLskYiwabbCQNNhl

After Matrix has restored its major services, they noticed that the GPG keys used for signing packages where compromised.

The key IDs are:

AD0592FE47F0DF61 (synapse)
E019645248E8F4A1 (Riot/Web)

Please make sure to no longer use those keys.

Matrix.org just announced they are back once more:

twitter.com/matrixdotorg/statu

Let's hope things stay up as they are. There are definitely some new challenges to tackle, which came up in their issue tracker:

github.com/matrix-org/matrix.o

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.

twitter.com/matrixdotorg/statu

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!

The homeservers are back up

It seems like they are missing some pictures right now, I guess those will come back later.

Make sure you change your password (and NickServ passwords) and happy chatting!

See you around

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:

matrix.org/blog/2019/04/11/sec

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.

If you wonder where the CodiMD community channel went, here is a short text explaining it:

community.codimd.org/t/communi

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: twitter.com/matrixdotorg/statu

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:

twitter.com/matrixdotorg/statu

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!

Looking for opinions on Flatpak isolation for .

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:

github.com/flathub/im.riot.Rio

If someone is into CPP or electron development, please have a look at:
github.com/electron/electron/p

By the way, for those of you who didn't already get the update: Riot 1.0.6 is available as flatpak

Do you know what's great? When things just work.

Do you know what's even greater? When you merge something, and it causes upgrades on at least a few hundred but maybe a few thousand devices and it just works.

Oh and by the way I merged 1.0.5 recently which is rolled out to all users who use it from there :)

Those of you who run an up-to-date Fedora version will get it installed automatically in background. Just great :)

flathub.org/apps/details/im.ri

The Riot 1.0.4 flatpak is out

Given that you run an up-to-date version of Gnome Software, it'll by installed automatically in background

Otherwise it's time to run `flatpak update`!

I'm now an official maintainer of the Riot flatpak on flathub

I will try to make sure that we get the latest and greatest version of Riot as flatpak as soon as possible.

Show more
Sheogorath's Microblog

This instance is the microblog to my blog. You'll probably find more recent content here while finding more elaborated content on the blog. Impressum / Datenschutz / Privacy