SAS verification - Emoji Verification

[deejayexe]

Hello @maxberger I've been checking your latest commits and have verified that it is correct. The device ID is added. However, right now, the only way to verify the bot is by opening two external sessions and verifying them manually. However, over time, errors such as WRN Failed to verify self-signing signature error="invalid signature" and WRN One-time key has invalid signature from device are received in the log, and also if u doing that when receive a notification every minute appears more errors.
According to the Mautrix Go documentation, would it be possible to implement SAS verification to be able to verify the bot by emojis, for example, and thus verify the bot?
Thanks 😉

[maxberger]

Hi,

Do you have any idea where to start looking? There is a verification helper package https://pkg.go.dev/maunium.net/go/mautrix/crypto/verificationhelper
But it does not come with any instructions.

When you try verification, with DEBUG on, do you see anything in the log? If so, could you paste that?

[deejayexe]

Hi
I've been looking at the documentation, but I'm no expert in Go, and I'm hardly a programming expert either.
I found that using the bot in multiple rooms caused problems, so I only had one bot for each room I needed.
I saw that you made changes and updated the container, but now it keeps restarting with this error:
2:46PM INF Gotify matrix bot v0.0.0-20250318221350-0a6e267faf06 has started.
2:46PM INF Starting main loop...
2:46PM INF Connected to Matrix.
panic: M_FORBIDDEN (HTTP 403): Cannot create filters for other users
goroutine 15 [running]:
gotify_matrix_bot/matrix.Connect.func2()
/app/matrix/matrixConnection.go:87 +0x65
created by gotify_matrix_bot/matrix.Connect in goroutine 1
/app/matrix/matrixConnection.go:84 +0x4cd

I see that now generated sqlite database (cryptoStore.db) and a config.generated.yaml with only brackets inside {}, tell me if you need help and I'll try what you tell me.

[maxberger]

Forgot the changes from yesterday; reusing the device ID messed up more than it did good.

I now completly went away with the device ID and the token; instead, you need to set the password. The Bot will then properly log-in, get a new device ID, and store it along with all other crypto-related material in the DB.

You may have to delete the old crypto DB; the generated config is now also obsolete again.

I have also found the SAS Helper; I already started experimenting with it, but the existing not-fully-working crypto has been in the way; I'll update here when I get that one to work.