https://bugs.kde.org/show_bug.cgi?id=377382
--- Comment #10 from Thomas Lübking <thomas.luebk...@gmail.com> --- Evolution has OAUTH2 support - it's not exaclty proprietary (that wouldn't make sense) but it's certainly far from unobjected, see https://en.wikipedia.org/wiki/OAuth#Controversy Leaving the complexity concerns aside, there's certainly usecase for such system, but it's not "your MUA wants to log into your IMAP server" but more like "webservice foo wants to use your google drive" which you can then individually permit and revoke that permission w/o having to expose (and thus later change) your credentials. Also I frankly wonder how google secures the OAUTH2 access of MUAs - "something™" will have to open a 2nd channel to google and have it ask for confirmation. If "someone" is your local client that opens a browser with a google link, I could imagine this is easily broken (by the local client never opening a visible webpage and just clicking "ok" for the user...) - so the client would have to tell the user "please log into your google account and allow me" *shrug* -- You are receiving this mail because: You are watching all bug changes.
