[5628] in Release_7.7_team

home help back first fref pref prev next nref lref last post

Request to make Pine deal with LDAP v3

daemon@ATHENA.MIT.EDU (oliver thomas)
Mon Oct 16 16:52:23 2006

Message-Id: <200610162052.k9GKqJlo023191@rogue.mit.edu>
To: release-team@MIT.EDU
Cc: oliver thomas <othomas@MIT.EDU>
Reply-To: oliver thomas <othomas@MIT.EDU>
Date: Mon, 16 Oct 2006 16:52:19 -0400
From: oliver thomas <othomas@MIT.EDU>
X-Spam-Score: 0.12
X-Spam-Flag: NO


The below request came into suggest@mit.edu and Owls asked me to forward it to
release-team for consideration. I've responded to the client to let him know
that it has been submitted as a request to be considered.

The request seems to indicate that there are two ways of doing this, one
via a small source code change and the other via upgrading to a more
recent version of pine.

Cheers,

Oliver

=====

Hello you wonderful Helpdesk person,

I was somewhat saddened to find that the current MIT version of Pine does
not recognize LDAPv3, so I went searching and found two possible
solutions.

1) Change a line of code in the file pine/bldaddr.c:


    int v3_is_supported_by_server = 0;

to

    int v3_is_supported_by_server = 1;

and

2) Pine v4.64 allows the user to connect with a LDAPv3 server even though
Pine does not yet have the full utf8 support.  This option in the
configuration of v4.64 is probably nothing more than a switch connected to
the variable in solution #1.

I can imagine that solution #2 is a lot more work, but #1 should not be
more work than changing the one character and recompiling.  Also, This fix
has already been tested.  (See

http://mailman1.u.washington.edu/pipermail/pine-info/2005-June/051329.html &
http://mailman1.u.washington.edu/pipermail/pine-info/2005-July/051369.html

).

It would be a great service to all of us who use Pine regularly for IS&T
to make this small change and make our lives significantly easier.

Thanks!

David Nawi

home help back first fref pref prev next nref lref last post