3 ms·
Authentication for email and other passive services is a bit trickier. For example suppose your mail server falls over, then is restarted. Does the mail client
by tialaramex 6y ago
Authentication for email and other passive services is a bit trickier.
For example suppose your mail server falls over, then is restarted. Does the mail client on your phone go "Hey, I need to re-authenticate to this server?" and meanwhile you don't receive any email? That's a not-great user experience.
For SMTP this is a bit less fraught because at least the user presumably just did something to cause sending, so we can ask them to authenticate at that point. But that still can be a bit trickier than you'd like.
There's also a much nastier backward compatibility story for email than for a relatively recent thing like GitHub. There absolutely will be a user with an Amiga 1200 using email on a big email service. Do you cut their service off? Maybe you have to, if that's the only way to secure service for other users. But it's a real last resort.
- dathinab 6y ago> For example suppose your mail server falls over, If token based authentication is affected by this your mail server is doing things very very wrong. ---- I'm well aware about all the problems involved when it comes to mail/smtp auth by now. Still username+password auth done by any client for anything but the initial sign-up is a latent security vulnerability even if it's currently tricky to fix. -------- > There absolutely will be a user with an Amiga 1200 using email on a big email service. Do you cut their service off? Yes, if I would be a mail company I most likely would not have any reason to support them tbh. Probably a better example would be outdated outlook versions ;=)