Re: Replication: problems with synctest

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



It looks like my problem with replication not working in one direction
was a SASL thing.  One of my servers was advertising GSSAPI as an
authentication mechanism, but it didn't really work (I don't have
Kerberos installed on my systems).  Apparently, sync_client on the
other box was deciding to use GSSAPI, but was giving up because it
wasn't actually functional.

I fixed the problem by moving the libgss* libraries out of the SASL2
library directory.

While I was at it, I also moved the libntlm* and libotp* libraries
out of the SASL2 library directory, since I'm not using either of
these authentication methods either.

I'm mildly concerned that a future software upgrade might cause these
libraries to reappear.  Is there a more reliable way to disable SASL
authentication mechanisms, other than removing files from the library
directory?

-- 
Rich Wales      ===      Palo Alto, CA, USA      ===     richw@xxxxxxxxx
http://www.richw.org   ===   http://en.wikipedia.org/wiki/User:Richwales
    "The difference between theory and practice is that, in theory,
theory and practice are identical -- whereas in practice, they aren't."
----
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

[Index of Archives]     [Cyrus SASL]     [Squirrel Mail]     [Asterisk PBX]     [Video For Linux]     [Photo]     [Yosemite News]     [gtk]     [KDE]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux