SZÉPE Viktor wrote in
<20220904221036.horde.ags-xf3y3wwighnghqtb...@szepe.net>:
|Hello folks!
|
|I'm not really into console based mailing. (maybe with v15 it will change!)
|
|In 2022 isn't it obvious that xoauth2 should be an integral part of
|your email client?
|This is only my feeling. My 15 year old self hosted Horde webmail is
|also oauth-less.
Well there is
Author: Steffen Nurpmeso <stef...@sdaoden.eu>
AuthorDate: 2019-09-08 03:12:08 +0200
Commit: Steffen Nurpmeso <stef...@sdaoden.eu>
CommitDate: 2022-08-24 01:43:44 +0200
[net-test] (BWDIC!) Extend authentication stuff, support automatic such..
In order to finally "just work" (tm), to reduce the number of
variables which need to be set to configure a single protocol, and
also to require lesser code once it is possible to do the
configuration also as part of an URL query string, rework the
authentication stuff a bit.
So with this we now have the framework to automatically handle
AUTHentication, by parsing those mechanisms which the server
supports, collate that with user wishes, and finally select the
best mechanism in the current context.
This also changes several other things:
- Add XOAUTH2 authentication (at least as a name).
This is BWDIC!, because we falsely claimed OAUTHBEARER to be
XOAUTH2 in the past.
- EXTERNAL and EXTERNANON require TLS.
- OAUTHBEARER and XOAUTH2 require TLS.
But unfortunately so much is still missing for v14.10, it will not
happen before Christmas for sure.
It did
case mx_CRED_AUTHTYPE_OAUTHBEARER:
+ case mx_CRED_AUTHTYPE_XOAUTH2: /* TODO XOAUTH2 == OAUTHBEARER */
f |= a_IS_OAUTHBEARER;
/* FALLTHRU */
case mx_CRED_AUTHTYPE_PLAIN:
- default: /* (this does not happen) */
....
#define a_MAX \
(2 + sizeof("AUTH XOAUTH2 " "user=\001auth=Bearer \001\001" NETNL))
...
if(f & a_IS_OAUTHBEARER){
authfmt = NETLINE("AUTH XOAUTH2 %s");
so i am pretty sure it _was_ XOAUTH2.
--steffen
|
|Der Kragenbaer, The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)
