I'm looking at @zulip as a possible option for the Asahi Linux chat, but I've already run into something concerning... It seems they trust verified e-mails from all of their authentication providers (GitHub / Gitlab / Google). This means their attack surface is *all* of those.
-
Show this thread
-
So even if you've never logged into
@zulip with@gitlab, if you have a Gitlab account and someone takes over it, they can take over your Zulip. If you don't have a Gitlab account and someone creates one and manages to verify your email on it, they can take over your Zulip.1 reply 0 retweets 14 likesShow this thread -
This seems... suboptimal. Third party log-ins should be linked explicitly, not implicitly via verified e-mails. I was confused, looking for that option in the settings and not finding it... then realized it was automagic via email matching.
2 replies 0 retweets 16 likesShow this thread -
Something something email canonicalization. Here be dragons.
2 replies 0 retweets 18 likesShow this thread -
Replying to @marcan42
What’s your threat model? An adversary takes over an account, now what bad can they do?
1 reply 0 retweets 0 likes
That, or someone somewhere has a different idea than you about email canonicalization. Or a service gets compromised and that now affects people who aren't users.
Like, if Gitlab gets owned the attacker can take over *all* @zulip accounts, not just those of Gitlab users.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.