On Thu, Jun 20, 2019 at 12:55 AM Steffen Nurpmeso <stef...@sdaoden.eu> wrote: > Steffen Nurpmeso wrote in <20190619234414.zvcpd%stef...@sdaoden.eu>: > ... > |Dear Ivan. If you are willing to test once again, at [1] there is > |a complete ball, but you could also simply apply the attached > |patch instead, which is very much smaller. > | > |I am sorry for the inconvenience, and i hope this fixes GSSAPI. > ... > > the patch was reversed; here is the right one.
You did not quote "the right one", but the master branch seems to use 6b070335 from the previous email, so I used that. If you mean the attachment, AFAICT it matches 6b070335 so that was already included. :-) > |No, this is actually success. I kdestroyed the ticket cache > |beforehand, and kinited. > > And isn't that cooler than OAUTH? And no advertising, neither > yesterday nor today and very likely also tomorrow not. It all comes down to scalability and scoping of non-password authentication on larger systems. OAuth2 is simpler than Kerberos, and doesn't (as generally implemented) depend on a secret being provided to obtain a TGT. But it's not why I brought it up earlier; XOAUTH2 (and other mechanism names used to represent this authentication method using a bearer token obtained through out-of-channel means, which can be a browser, but don't have to be) is just one of many SASL mechanisms you'd get for free. > I should have warned you that the password and credentials will be > included in the debug output. No, it's to be expected if it's obvious that there's raw IMAP protocol being logged. That's why I took care and removed what looked like credentials. (Thankfully, I'm familiar enough with IMAP anyway.) > ..../6b070335d77251308e1910f9efb2e08754a1f176 Thank you, this has fixed it. I was seeing this, though: ``` s-nail: s-nail version v14.9.13. Type `?' for help +[imap://ivuc...@myhostname.ds.mydomain.net/]INBOX: 3 messages ▸O 1 xxxxxx 2019-01-29 03:15 /40755 aaaaaaaa O 2 xxxxxxx 2019-02-01 09:58 /31642 aaaaaaaaa O 3 xxxxxxx. 2019-01-28 15:34 /24693 aaaaaaa There are new messages in the error message ring (denoted by ERROR) It can be managed with the `errors' command ERROR# ? errors 1. ? errors The error ring is empty ? q Held 3 messages in +[imap://ivuc...@myhostname.ds.mydomain.net/]INBOX ``` I'm not sure how to use the 'errors' command or where this error came from. In the meantime I cleaned the inbox, so I am no longer seeing this error and probably can't easily reproduce it. Either way, the original bug is now gone from upstream, so if experimental were updated to 6b070335d77251308e1910f9efb2e08754a1f176 or later, that would solve debian bug #930691.
