Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Could you expand on that? How is OAuth 2.0 fundamentally insecure in this setting?


It makes it necessary to use a browser to obtain the token. That browser is a huge attack surface. With web, it doesn’t matter, since you need to be using it anyway, but for mail it’s just additional cruft.


That's just for certain flows, like the common authorization code flow. The client credentials flow does not require a browser, for example.

Not sure about Google, but Microsoft supports client credentials for IMAP/POP3[1], but not for SMTP yet. IIRC it was supposed to be rolled out this January but is still missing. Hopefully they can get that deployed ASAP.

[1]: https://learn.microsoft.com/en-us/exchange/client-developer/...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: