Oswald Buddenhagen <[email protected]> writes: > On Mon, Sep 08, 2014 at 01:02:30PM +0200, Jan Synacek wrote: >> Oswald Buddenhagen <[email protected]> writes: >> >On Fri, Jul 04, 2014 at 11:29:52AM +0200, Jan Synacek wrote: >> >> Here's second version of my patch. I decided to kind of revive (I >> >> cleaned it up a lot) the original sasl branch. Since the SASL support >> >> will already be there, I don't think it makes sense to have additional >> >> code for GSSAPI only. >> >> >> > so i finally had a go at it. >> > the sasl branch contains my new version (on top of a lot of ssl stuff >> > which is basically totally unrelated, but which i found the need for >> > while trying to understand the surrounding code :D). >> > it's tested with PLAIN (and LOGIN). >> >> I just noticed this... I'm not subscribed to the mailing list and I >> wasn't on the CC. >> >> Your implementation misses GSSAPI support, which is the main reason for >> my original patch. >> > ehm. have you tried?
Ah, sorry for the confusion, I was reading the output wrong... Yes, I have tried and I'm getting: ... Authenticating with SASL mechanism GSSAPI... Error: SASL provided no authentication data. Error: (null) I have a valid kerberos ticket. Cheers, -- Jan Synacek Software Engineer, Red Hat ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce. Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ isync-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/isync-devel
