On 08/04, Oswald Buddenhagen wrote:
On Tue, Apr 07, 2015 at 09:48:07PM +0200, Johannes Löthberg wrote:I just noticed that GSS-API authentication was broken, and after a while I noticed that it was due to updating isync. The commit that broke it was 138983c91edbb8d2176f5658607d80758dfbcf56. With that commit mbsync will try to authenticate as kyr...@kyriasis.com even though I have `User kyrias` set in my mbsyncrc*sniff* USER is the local user who is attempting to authenticate. this can't be trusted unless the caller is (setuid) root, so it *shouldn't* have much of an impact. AUTHNAME is the user to authenticate *as*, for whom PASS is. so the patch should be ok. the question is where the @kyriasis.com comes from.
Very good question, because it’s not set at all in my config file.
as an experiment, you could half-revert the patch, so mbsync would pass both user and authname with the same value (which is in fact what an earlier version of the sasl patch did). if that works, i'd venture that the sasl module writers are just as confused about the variable names as i was ...
Do you mean like only adding back what 138983c91e removed, keeping what it added? Because if so it works fine.
-- Sincerely, Johannes Löthberg PGP Key ID: 0x50FB9B273A9D0BB5 https://theos.kyriasis.com/~kyrias/
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
