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

brokerAuth.request() also sends tiny proof of ownership #4

Open
staltz opened this issue Jan 28, 2022 · 2 comments
Open

brokerAuth.request() also sends tiny proof of ownership #4

staltz opened this issue Jan 28, 2022 · 2 comments

Comments

@staltz
Copy link
Owner

staltz commented Jan 28, 2022

Problem: avoid spam from attackers trying to use the room alias. If anyone with a new app can input my alias, then that could cause a popup on my app asking for approval. The popups can get too intrusive if it's about an attacker and I have to reject them every time.

Idea: When the new app sends brokerAuth.request() it can also send a partial proof that it owns the same SSB ID, sort of like a "password". It could be the 1st word in the 24 words phrase. The "proofword".

This would create a lot more friction to brute force attacks because the room can detect that an attacker is calling too many brokerAuth.request()s and ban the attacker based on SSB ID or IP. And even in the worst case where the attacker guesses the correct 1st word (out of 2048 words), the effect is not a breach, it's simply that the old app would show the popup asking for permission.

@Powersource
Copy link

my cryptography senses are tingling that this isn't a great idea but i can't back that up lol

@staltz
Copy link
Owner Author

staltz commented Jan 28, 2022

I miss keks for those kinds of things

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

2 participants