Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Manual device verification e.g. for bots like Mjolnir #2751

Open
Tracked by #2700
andybalaam opened this issue Feb 24, 2025 · 1 comment
Open
Tracked by #2700

Manual device verification e.g. for bots like Mjolnir #2751

andybalaam opened this issue Feb 24, 2025 · 1 comment

Comments

@andybalaam
Copy link
Member

andybalaam commented Feb 24, 2025

When we start excluding unsigned devices then all users in a room, including bots, will need to verify their devices.

Some bots, e.g. mjolnir don't currently provide a way to verify their devices, and the underlying matrix-bot-sdk does not provide a way of doing this. The preferred way would be to supply a Recovery Key during bot setup, but without support in matrix-bot-sdk this would be quite a lot of development work to do.

So, we want an easier way of manually asserting that a device is verified. We think the simplest way would be for the bot to print out its ed25519 key on startup, so we can supply it to another client.

Probably in Element Web, we should provide a dialog (probably in an "Advanced" section) that allows pasting in a client's ed25519 key to verify it. Note: @Half-Shot pointed out that some people would find this much easier if it were part of the ESS management console or even a custom tool, rather than Element Web. On the other hand, for community use, putting it in ESS would not help.

@andybalaam
Copy link
Member Author

andybalaam commented Feb 24, 2025

This is a proposed solution to the problem described in #2709

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant