4 ms·
I love the idea of using Matrix as a federated login system. This implementation however, is not acceptable. You shouldn't enter your username and password for
by jeroenhd 5y ago
I love the idea of using Matrix as a federated login system. This implementation however, is not acceptable.
You shouldn't enter your username and password for one website into another. You shouldn't train users to do so either. Using this reinforces the problematic security behaviour every company had been trying to unteach users for ages.
I think the concept is great, but there should be an OAuth callback running on the homeserver, where the user perhaos enter their password, rather than a login form embedded into the website itself. This shouldn't be impossible to accomplish with a little companion tool you can run on your homeserver to receive and deal with callbacks. There'd be no need for the server admins to choose which applications to integrate to or not, just plonk it behind a proxy and you're done. That way, the mapping between URL and credentials remains and the impact on server administrator workload should be minimal. Of course, there's still a need for a good security strategy to make sure the OAuth UI doesn't get hijacked, but the concept is a lot more workable than this example.
- ushakov 5y agoI will be adding more (secure) methods as soon as the protocol supports this
- tata71 5y agoU2F?
- kadoban 5y agoUntil then, is there _any_ safe way to use this? I do not think there is.
- ushakov 5y agouse a burner account
- kadoban 5y agoAs software engineers, we really need to consider not just if we can do a project, but also if we _should_. If the only way a project can be used safely is with a burner account, should this actually be released? It does not appear to have any warnings on it either.
- ushakov 5y agoit's my project and you can choose to not use it
- oefrha 5y ago(Disclaimer: not a security expert, opinions could be wrong.) > You shouldn't enter your username and password for one website into another. A stronger version of this is you shouldn't embed any kind of authentication/authorization widget of one website into another, even if the widget is supposedly under complete control of the auth provider (i.e. an iframe). For instance, is an embedded SSO widget without password entry okay? No. Cue Google YOLO clickjacking.[1][2] There's a reason OAuth forbids iframe embedding and even recommends JS frame-busting on browsers that don't support X-Frame-Options.[3] [1] https://blog.innerht.ml/google-yolo/ https://blog.innerht.ml/google-yolo/ [2] https://news.ycombinator.com/item?id=17044518 https://news.ycombinator.com/item?id=17044518 [3] https://datatracker.ietf.org/doc/html/rfc6749#section-10.13 https://datatracker.ietf.org/doc/html/rfc6749#section-10.13
- klabb3 5y ago> You shouldn't enter your username and password for one website into another. You shouldn't train users to do so either. I'd even argue that this is the much bigger point. The only practical way we have to avoid phishing (and its cousins) with password-only auth is teaching users to look at the domain-part of the URL. It's the only thing I can currently teach my non-technical friends & family. Human assumptions are basically software that takes years or decades to upgrade, among other problems. Can't really stress enough how important it is to foster and teach best practices in this space. It's a giant shitshow to reverse these things. Fortunately, Matrix is still nothing my grandmother would use, but it would really suck for Matrix if they have yet-another hurdle to overcome in reaching the mainstream. If I were Matrix, I'd be extremely concerned with this.