Re: [Evolution] ldap protocol problems



The server is openldap-1.2.9-5 (an old RH 6.2 box).  And I'm using TLS =
never.  So, it sounds like I'm pretty much out of luck with this version
of openldap?  And did this change between evo 1.0.8 and 1.2.0?

On Mon, 2002-11-25 at 23:29, Chris Toshok wrote:
At present evolution sets the connection to v3 when it initializes it,
and there's no setting to drop the protocol to v2.  Which server are you
running?

The setting is mostly there because of the TLS stuff, so potentially it
could be done only in the case where use_tls != never.

Chris

On Mon, 2002-11-25 at 06:46, Jason 'vanRijn' Kasper wrote:
I'm running debian sid and using evolution 1.2.0 with the below LDAP
versions installed.  Evolution version 1.0.8 used to work just fine and
dandy with the LDAP server at my work, but 1.2.0 now reports "We were
unable to open this addressbook. This either means you have entered an
incorrect URI, or the LDAP server is unreachable."  

Mind you, none of my settings for this LDAP server have changed between
version 1.0.8 (where it was working), and 1.2.0 (where it's not).  

I've played with the command-line "ldapsearch" utility and it looks to
me like my LDAP server isn't able to handle protocol version 3, but if I
force it to use protocol version 2 (by using "-P 2"), ldapsearch is able
to talk to the server.  

So, my question...  Is it possible to force evolution to use a specific
LDAP protocol version for its lookups?  Or, is there a proper way to get
evolution to talk to my LDAP server again?  =:)

TIA!!

ii  ldap-utils     2.0.23-14      OpenLDAP utilities.
ii  libldap2       2.0.23-14      OpenLDAP libraries (without TLS support).
ii  libldap2-dev   2.0.23-14      OpenLDAP development libraries.
-- 

,-----------------------------------------------------------------//
| Jason 'vanRijn' Kasper ::  Numbers 6:22-26 
 `
 | All brontosauruses are thin at one end, much MUCH thicker 
 | in the middle, and then thin again at the far end.  That is 
 | the theory that I have and which is mine, and what it is too.  
 ,
| bash$ :(){ :|:&};:
`----------------------//




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