Spurious 'upgrade encryption' toast

[dbkr]

Seems like it's possible it get 'Upgrade encryption' toasts when everything set up fine: possibly a race where the tests for whether encryption is set up can be run before everything's ready?

Edit: It happens every time the user starts the app, so must be that something is in a weird state where the checks don't think everything's set up but then the bootstrap doesn't do anything.

Rageshake linked.

[dbkr]

Also not sure the room upgrades tag is relevant here: room upgrade !== encryption upgrade

[SimonBrandner]

I could have sworn there was room upgrade in the title 🤣

[schildbach]

Just for reference, here is a screenshot of the toast.

Encryption upgrade available

Safeguard against losing access to encrypted messages & data

[Palid]

This also happens on the MacOS Desktop version. I can attach some additional logs if necessary.

[dbkr]

Looks like we probably fixed a check in the typescript conversion and now this is checking that the key backup key is in SSSS (secure secret storage and sharing), which is isn't for some people (probably account old enough to have key backup before it was cool SSSS. Hitting the upgrade button should prompt for the SSSS passphrase and save the key backup key to SSSS.

Other possibility is that these are accounts with a transitional 'identity' entry in SSSS (ie. declaring that the key backup secret is the same as the SSSS master key) and element isn't recognising this.

[dbkr]

Anyone who's getting this: could you check whether you have your key backup key stored, as follows:

1. Open devtools by typing /devtools and pressing enter in the composer in any room
2. Click 'Explore Account Data'
3. Look for m.megolm_backup.v1
4. If it's there, click it

I'm interested in a) whether m.megolm_backup.v1 is there at all and if it is, whether it's a structure with iv / ciphertext / mac in it or just passthrough, or something else (don't post actual screenshots: it's all encrypted but still, no reason to let the world try cracking your key backup key).

eg. my account has:

[schildbach]

For me, m.megolm_backup.v1 is not present. However I'm using encryption since day 1 (3 years) ago, and I have all sorts of key backups. Is there reason to worry?

[evoL]

Same for me, m.megolm_backup.v1 is not present at all. The account is from 2018.

Edit: I should also mention that hitting Upgrade flashes a spinner for a split second and does nothing afterwards. The toast is still there.

[valkum]

m.megolm_backup.v1 is missing for me as well. Account is on a private homeserver and from around 2017.

[dbkr]

Thanks all - seems like your backup key has just not made it into secret storage at all then.