gqclient-discuss Mailing List for GQ LDAP client (Page 36)

First I would like to say that this is a great, EASY to use and install
ldap client! I tried to install various different ldap clients on a
Linux Redhat 6.2 - all except gq needed additional libraries, didn't
compile etc ...

I'm running gq on Linux Redhat 6.2 with latin-1 as the default charset.

At the moment I get national characters into the database through an
ldif file:

1. write data (including special danish letters) in latin-1 code
2. run "tcs -f 8859-1 oldfilename > newfilename (this maps latin-1 chars
into utf8)
3. use ldapadd

Note: tcs is available from:
ftp://plan9.bell-labs.com/plan9/unixsrc/tcs.shar.Z

However, it would be nice to be able to do this directly through gq -
perhaps through some built-in "tcs"-functionality ??

Thanks in advance

Michael

On Wed, 11 Oct 2000, Kalman KK Wan wrote:

> I'm installing gq0.3. When I run "./configure", I got the following error:
> 
> checking for ldap_simple_bind in -lldap... no
> configure: error: Cannot find libldap

Take a look at the file config.log, generated by autoconf. There should be
some indication there as to why the test failed.


Bert Vermeulen
be...@bi...
--
Yes, I am an agent of Satan, but my duties are largely ceremonial.

I'm installing gq0.3. When I run "./configure", I got the following error:

checking for ldap_simple_bind in -lldap... no
configure: error: Cannot find libldap

I have installed OpenLDAP V2 and it is working. I have the following files in
/user/local/include:
ldap.h
ldap_cdefs.h
ldap_features.h
ldap_schema.h

I also have the following files in /user/local/lib:
libldap.a
libldap.la
libldap_r.a
libldap_r.la
libldap_r.so
libldap_r.so.2
libldap_r.so.2.0.3
libldap.so
libldap.so.2
libldap.so.2.0.3

I have tried "./configure --with-ldap-prefix=/usr/local" also, but I got the
same error.
Please help. Thanks.

Hi All,

Platform:
--------

SunOS banquo 5.7 Generic_106541-11 sun4u sparc SUNW,Ultra-5_10

Configured with:
---------------

CC=gcc CFLAGS=-O3 CPPFLAGS='-I/usr/local/ssl/include' LDFLAGS='-L/usr/local/ssl/lib' ./configure

Result:

checking for ldap_simple_bind in -lldap... no
configure: error: Cannot find libldap

config.log
----------

configure:1320: checking for ldap_simple_bind in -lldap
configure:1339: gcc -o conftest -O3 -I/usr/local/lib/glib/include -I/usr/local/include -I/usr/openwin/include
-I/usr/local/
ssl/include -L/usr/local/ssl/lib conftest.c -lldap -llber -lresolv  -L/usr/local/lib -L/usr/openwin/lib
-R/usr/openwin/lib 
-lgtk -lgdk -lgmodule -lglib -ldl -lXext -lX11 -lsocket -lnsl -lm 1>&5
Undefined                       first referenced
 symbol                             in file
SSL_library_init                    /usr/local/lib/libldap.so
ERR_error_string                    /usr/local/lib/libldap.so
SSL_CTX_set_cipher_list             /usr/local/lib/libldap.so
SSL_CIPHER_get_bits                 /usr/local/lib/libldap.so
CRYPTO_free                         /usr/local/lib/libldap.so
X509V3_add_standard_extensions      /usr/local/lib/libldap.so
X509_get_issuer_name                /usr/local/lib/libldap.so
SSLv23_method                       /usr/local/lib/libldap.so
X509_STORE_CTX_get_current_cert     /usr/local/lib/libldap.so
SSL_shutdown                        /usr/local/lib/libldap.so
X509_free                           /usr/local/lib/libldap.so
SSL_state_string_long               /usr/local/lib/libldap.so
X509_STORE_CTX_get_error_depth      /usr/local/lib/libldap.so
SSL_CTX_use_PrivateKey_file         /usr/local/lib/libldap.so
SSL_CTX_set_tmp_rsa_callback        /usr/local/lib/libldap.so
SSL_CTX_set_verify                  /usr/local/lib/libldap.so
X509_STORE_CTX_get_error            /usr/local/lib/libldap.so
SSL_CTX_check_private_key           /usr/local/lib/libldap.so
SSL_CTX_free                        /usr/local/lib/libldap.so
SSL_alert_type_string_long          /usr/local/lib/libldap.so
SSL_set_info_callback               /usr/local/lib/libldap.so
SSL_load_error_strings              /usr/local/lib/libldap.so
SSL_alert_desc_string_long          /usr/local/lib/libldap.so
SSL_get_current_cipher              /usr/local/lib/libldap.so
SSL_CTX_set_client_CA_list          /usr/local/lib/libldap.so
SSL_CTX_use_certificate_file        /usr/local/lib/libldap.so
SSL_set_bio                         /usr/local/lib/libldap.so
SSL_connect                         /usr/local/lib/libldap.so
SSL_CTX_new                         /usr/local/lib/libldap.so
X509_get_subject_name               /usr/local/lib/libldap.so
RSA_generate_key                    /usr/local/lib/libldap.so
SSL_CTX_set_default_verify_paths    /usr/local/lib/libldap.so
SSL_write                           /usr/local/lib/libldap.so
SSL_CTX_load_verify_locations       /usr/local/lib/libldap.so
SSL_new                             /usr/local/lib/libldap.so
BIO_new                             /usr/local/lib/libldap.so
SSL_get_error                       /usr/local/lib/libldap.so
ERR_get_error_line                  /usr/local/lib/libldap.so
SSL_load_client_CA_file             /usr/local/lib/libldap.so
SSL_free                            /usr/local/lib/libldap.so
ERR_peek_error                      /usr/local/lib/libldap.so
SSL_get_peer_certificate            /usr/local/lib/libldap.so
SSL_read                            /usr/local/lib/libldap.so
SSL_accept                          /usr/local/lib/libldap.so
X509_NAME_oneline                   /usr/local/lib/libldap.so
ld: fatal: Symbol referencing errors. No output written to conftest
collect2: ld returned 1 exit status
configure: failed program was:
#line 1328 "configure"
#include "confdefs.h"
/* Override any gcc2 internal prototype to avoid an error.  */
/* We use char because int might match the return type of a gcc2
    builtin and then its argument prototype would still apply.  */
char ldap_simple_bind();

int main() {
ldap_simple_bind()
; return 0; }



ldap 2.0.3 is installed in /usr/local (standard location).

What's going on here?

Thanks,


Jie

The following message I get when trying to compile gtk

checking for GTK - version >= 1.2.0... no
*** The gtk-config script installed by GTK could not be found
*** If GTK was installed in PREFIX, make sure PREFIX/bin is in
*** your path, or set the GTK_CONFIG environment variable to the
*** full path to gtk-config.
configure: error: Cannot find GTK: Is gtk-config in path?

I do not see gtk-config in the tar file.

Eli

On Fri, 15 Sep 2000, Chris Alberry wrote:

> Any idea how I resolve this error making GQ.  I can't find the four LDAP_*
> errors defined anywhere.

[...]

> schemabrowse.h:43: parse error before `LDAP_OBJECT_CLASS'
> schemabrowse.h:48: parse error before `LDAP_ATTRIBUTE_TYPE'
> schemabrowse.h:53: parse error before `LDAP_MATCHING_RULE'
> schemabrowse.h:58: parse error before `LDAP_SYNTAX'

GQ 0.2.3's schema code was written to compile against openldap-devel. Since
then, however, some changes were made to openldap-devel, including the
definitions above. It has since been released as openldap 2.0.

Just grab the latest GQ out of the sourceforge CVS, it should compile fine
against current openldap 2.x. Do let me know how it works for you, as I'm
looking to release it soon...

...if only it would still work with openldap 1.2.x :-(


Bert Vermeulen
be...@bi...
--
Yes, I am an agent of Satan, but my duties are largely ceremonial.

Any idea how I resolve this error making GQ.  I can't find the four LDAP_*
errors defined anywhere.

Thanks
Chris

Linux Server1 2.2.16-3 #1 Mon Jun 19 18:10:14 EDT 2000 i686 unknown
[root@Server1 gq-0.2.3]# make
make  all-recursive
make[1]: Entering directory `/home/download/GQ/gq-0.2.3'
Making all in src
make[2]: Entering directory `/home/download/GQ/gq-0.2.3/src'
gcc -DHAVE_CONFIG_H -I. -I. -I..     -g -O2 -I/usr/lib/glib/include -I/usr/X
11R6
/include -Wall -c mainwin.c
In file included from mainwin.c:41:
schemabrowse.h:43: parse error before `LDAP_OBJECT_CLASS'
schemabrowse.h:48: parse error before `LDAP_ATTRIBUTE_TYPE'
schemabrowse.h:53: parse error before `LDAP_MATCHING_RULE'
schemabrowse.h:58: parse error before `LDAP_SYNTAX'
make[2]: *** [mainwin.o] Error 1
make[2]: Leaving directory `/home/download/GQ/gq-0.2.3/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/download/GQ/gq-0.2.3'
make: *** [all-recursive-am] Error 2

Aloha!

as Bert at Biot.com is Dutch person, I sent it in Dutch, ooops... so for all
the other people: I installed $subject and have no problems changing
records, but if I choose 'New', 'Current Entry', it does nothing. I suppose
that I can add a record at that moment??

Regards
Mark

On Mon, 28 Aug 2000, Tonny Gisbertz wrote:

> Any ideas why this would occur?  I can search with no problems, but the
> app pukes when I attempt to browed the tree.  Probably something stupid
> on my part, but who knows....

Regardless what the problem is, gq shouldn't segfault. Could you try with
the latest version out of CVS, and see if browsing still fails?

Alternatively, run it through gdb and send a backtrace, so I know where to
look.


Bert Vermeulen
be...@bi...
--
Yes, I am an agent of Satan, but my duties are largely ceremonial.

Any ideas why this would occur?  I can search with no problems, but the
app pukes when I attempt to browed the tree.  Probably something stupid
on my part, but who knows....

TIA,


-Jeff

On Wed, Jun 07, 2000 at 12:57:21AM +0200, Bert Vermeulen wrote:
> On Tue, 6 Jun 2000, Adrian Likins wrote:
> 
> > 	anyone having any luck gettings gq to see anything
> > in an NDS 8 eDirectory (on linux, if it matters...).
> > 
> > 	I can add the entry, and connect, but nothing
> > shows up in browse mode, just an error about "no suffixes found". 
> > Giving it the same basedn I use for everything else doesnt help.
> > NDS has been setup to allow clear text passwds, and GQ is binding
> > properly (and in fact, searching the tree returns valid entries),
> > just nothing in browse mode. 
> 
> Novell NDS doesn't seem to publish any suffixes. I'm not entirely sure if
> it's supposed to be LDAP V3 compliant or not...
> 
> I've added a patch in CVS to use the configured base DN as a last resort
> suffix. This works for me when testing with www.nldap.com:389 (o=novell).
> Let me know how this works for you.

	Cool. Seems to work here. Thanks.

Adrian

On Tue, 6 Jun 2000, Adrian Likins wrote:

> 	anyone having any luck gettings gq to see anything
> in an NDS 8 eDirectory (on linux, if it matters...).
> 
> 	I can add the entry, and connect, but nothing
> shows up in browse mode, just an error about "no suffixes found". 
> Giving it the same basedn I use for everything else doesnt help.
> NDS has been setup to allow clear text passwds, and GQ is binding
> properly (and in fact, searching the tree returns valid entries),
> just nothing in browse mode. 

Novell NDS doesn't seem to publish any suffixes. I'm not entirely sure if
it's supposed to be LDAP V3 compliant or not...

I've added a patch in CVS to use the configured base DN as a last resort
suffix. This works for me when testing with www.nldap.com:389 (o=novell).
Let me know how this works for you.


Bert Vermeulen
be...@bi...
--
Yes, I am an agent of Satan, but my duties are largely ceremonial.

	anyone having any luck gettings gq to see anything
in an NDS 8 eDirectory (on linux, if it matters...).

	I can add the entry, and connect, but nothing
shows up in browse mode, just an error about "no suffixes found". 
Giving it the same basedn I use for everything else doesnt help.
NDS has been setup to allow clear text passwds, and GQ is binding
properly (and in fact, searching the tree returns valid entries),
just nothing in browse mode. 

	This is with current cvs gq.

Adrian

On 16 May, Bert Vermeulen wrote:
> I've run into something of a snag here. I always thought I could work out by
> the schema how to display an attribute type's values. Looking at it a bit
> closer, though, it seems that kind of information just isn't there.
> 
> Am I missing something?
> 
> If not, I can see no other option than to implement Yet Another tab in
> Preferences, with something like a "schema helper". This would then allow
> you to edit a list of attribute types that should be considered a password
> or JPEG or whatever (passwords will have a combo box next to them containing
> the crypt type used).

After a quick look at rfc2252, you should have enough information. The
schema should have information like 

attributetypes=( 0.9.2342.19200300.100.1.60 NAME 'jpegPhoto' DESC 'Standard Attribute' SYNTAX '1.3.6.1.4.1.1466.115.121.1.5' )
attributetypes=( 0.9.2342.19200300.100.1.1 NAME 'uid' DESC 'Standard Attribute' SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' )
attributetypes=( 1.3.6.1.1.1.1.0 NAME 'uidNumber' DESC 'Standard Attribute' SYNTAX '1.3.6.1.4.1.1466.115.121.1.27' SINGLE-VALUE )

The syntax field describes the data format (rfc2252 has a list of
current syntaxes)

   Binary                          N  1.3.6.1.4.1.1466.115.121.1.5
   Directory String                Y  1.3.6.1.4.1.1466.115.121.1.15
   INTEGER                         Y  1.3.6.1.4.1.1466.115.121.1.27

Now, the rfc does have an entry for JPEG

   JPEG                            N  1.3.6.1.4.1.1466.115.121.1.28

but the netscape server I pulled this from seems to default to
"binary".

-- 
Doug Nazar
Dragon Computer Consultants Inc.
Tel: (416) 708-1578     Fax: (416) 708-8081

I've run into something of a snag here. I always thought I could work out by
the schema how to display an attribute type's values. Looking at it a bit
closer, though, it seems that kind of information just isn't there.

Am I missing something?

If not, I can see no other option than to implement Yet Another tab in
Preferences, with something like a "schema helper". This would then allow
you to edit a list of attribute types that should be considered a password
or JPEG or whatever (passwords will have a combo box next to them containing
the crypt type used).

Opinions?


Bert Vermeulen
be...@bi...
--
Yes, I am an agent of Satan, but my duties are largely ceremonial.

On Tue, 9 May 2000, William Webber wrote:

> Hi all!
> 
> I got a compile error for version 0.2.3.  Basically, the entire file
> tinput.c was ifdef'ed out by the #ifdef HAVE_LDAP_STR2OBJECTCLASS at
> the top, even though this symbol was defined elsewhere in the source.
> I fixed this for myself by putting a #include <config.h> above this
> ifdef, but I'm not cluey enought about the workings of ./configure to
> know whether this is the correct way to fix the problem.

Yes, a similar change has already been made in the CVS version.

Best check it out, lots of other things have changed since then :-)


Bert Vermeulen
be...@bi...
--
Yes, I am an agent of Satan, but my duties are largely ceremonial.

Hi all!

I got a compile error for version 0.2.3.  Basically, the entire file
tinput.c was ifdef'ed out by the #ifdef HAVE_LDAP_STR2OBJECTCLASS at
the top, even though this symbol was defined elsewhere in the source.
I fixed this for myself by putting a #include <config.h> above this
ifdef, but I'm not cluey enought about the workings of ./configure to
know whether this is the correct way to fix the problem.

William
-- 
William Webber                               wi...@pe...
Senior Programmer                             
PeopleWeb Australia                          http://www.peopleweb.com

On Mon, 8 May 2000, Ross Golder wrote:

> Out of interest, what distro are you using?

Some mongrel distribution, loosely redhat-5.1 based at some point :-)

> You sound like you've had a bad experience with GNOME?

No, not really. I don't much care for the desktop environment, but then
that's a personal preference, of course.

> Agreed, it's slick and you are very right to be proud of it. I did not
> mean any disrespect to your code by my suggestion.
> 
> As I said, I'll do the conversion anyway, as a personal exercise in
> GNOME, but I'll not commit my changes back. Or perhaps I could maintain
> my changes on a seperate 'GNOME' CVS branch, and maintain it in parallel
> with HEAD? I'll also try the #ifdef thing, to see if that becomes too
> hairy.

Sounds like a good plan. I would say, try both -- a second branch with
#ifdefs in it for Gnome. Like I said, there must surely be things you can do
to integrate better with Gnome, and that's a Good Thing.


Bert Vermeulen
be...@bi...
--
Yes, I am an agent of Satan, but my duties are largely ceremonial.

Bert Vermeulen wrote:
> 
> Of course I know what Gnome is :-)
> 

I thought so! I doubted that someone as adept at GTK+ as yourself
wouldn't have come across it.

> I don't use it as my desktop, and I don't know all that many people who do,
> or even have the libs on their system. Every distribution these days comes
> with GTK+ though, so converting GQ to Gnome would basically mean restricting
> the audience.
> 

Yes, that is true.

Out of interest, what distro are you using?

> I'm quite proud of the GQ user interface, it's about as slick as you can
> make it in GTK+. A far cry most most Gnome apps, with "Help" buttons that
> don't do anything etc.
> 

You sound like you've had a bad experience with GNOME?

Agreed, it's slick and you are very right to be proud of it. I did not
mean any disrespect to your code by my suggestion.

As I said, I'll do the conversion anyway, as a personal exercise in
GNOME, but I'll not commit my changes back. Or perhaps I could maintain
my changes on a seperate 'GNOME' CVS branch, and maintain it in parallel
with HEAD? I'll also try the #ifdef thing, to see if that becomes too
hairy.

Regards,

--
Ross

On Mon, 8 May 2000, Ross Golder wrote:

> It doesn't really have any significant advantages over the current
> method, except maybe the gimmicky 'tear-off' tab at the side. I was more
> interested in just integrating GNOME into my desktop. As a GTK+ app, GQ
> looks a bit strange amongst my other GNOME application windows, and it
> does have a slightly different look'n'feel as far as the end-user is
> concerned.
> 
> I kind of assumed that GTK+ people would have naturally progressed on to
> GNOME. As you and Bert don't appear to be using GNOME (what do you
> use?), I'm not sure if you genuinely don't know about GNOME, or whether
> you are just being sarcastic ;). If it's the former, then check out
> <http://developer.gnome.org> for more info. I've been using it for a
> year or two, and it's brilliant. Most Linux end-users will be using it,
> as it now comes bundled with most Linux distros. As I'm learning to
> develop GNOME applications at the moment anyway, I thought I could apply
> the time and effort I'm spending on it to improving the GQ user
> interface.

Of course I know what Gnome is :-)

I don't use it as my desktop, and I don't know all that many people who do,
or even have the libs on their system. Every distribution these days comes
with GTK+ though, so converting GQ to Gnome would basically mean restricting
the audience.

I'm quite proud of the GQ user interface, it's about as slick as you can
make it in GTK+. A far cry most most Gnome apps, with "Help" buttons that
don't do anything etc.


Bert Vermeulen
be...@bi...
--
Yes, I am an agent of Satan, but my duties are largely ceremonial.

na...@dr... wrote:
> 
> On  7 May, Ross Golder wrote:
> > Would patches that make GQ a GNOME application offend anyone?
> >
> > For example, I'm thinking of converting the menu bar to a GNOME menu
> > bar. As this would mean a new library dependency, I thought I best
> > check.
> 
> For those of us not running gnome, what is a Gnome menu bar? What
> advantages does it have?
> 

A GNOME menu bar is a widget provided by the GNOME libraries that makes
it easier for the programmer to implement a menu in his application.

It doesn't really have any significant advantages over the current
method, except maybe the gimmicky 'tear-off' tab at the side. I was more
interested in just integrating GNOME into my desktop. As a GTK+ app, GQ
looks a bit strange amongst my other GNOME application windows, and it
does have a slightly different look'n'feel as far as the end-user is
concerned.

I kind of assumed that GTK+ people would have naturally progressed on to
GNOME. As you and Bert don't appear to be using GNOME (what do you
use?), I'm not sure if you genuinely don't know about GNOME, or whether
you are just being sarcastic ;). If it's the former, then check out
<http://developer.gnome.org> for more info. I've been using it for a
year or two, and it's brilliant. Most Linux end-users will be using it,
as it now comes bundled with most Linux distros. As I'm learning to
develop GNOME applications at the moment anyway, I thought I could apply
the time and effort I'm spending on it to improving the GQ user
interface.

I'm gonna try to convert it anyway, and do a couple of screenshots for
you (before and after) while I'm at it. I'm sure I've got more important
things to do than fix what ain't broke, but this one seems to interest
me unnaturally. However, if it turns out to be a mess of #ifdefs to keep
things backward(?)-compatible, then I'll probably just drop it.

Anyway, I'm not up-to-speed on openldap enough yet to contribute in any
other way :)

Regards,

--
Ross

On Sun, 7 May 2000 na...@dr... wrote:

> Looking at the code, get_server_schema() just does a simple ldap_search
> to the server and then uses some local functions (ldap_str2objectclass
> and friends) to parse the info. That same info that was retrieved could
> have come from an openldap 1.x server.

But where will you get the OIDs?

> Yes, you do need an openldap 2.x client library to support it but you
> could easily use an openldap 1.x server to provide the information.

It's apparently something of a bear. From what I understand the schema
information that openldap-devel publishes isn't tied in to what it actually
uses as schema all that well (or wasn't a couple months ago, anyway).


Bert Vermeulen
be...@bi...
--
Yes, I am an agent of Satan, but my duties are largely ceremonial.

On  7 May, Bert Vermeulen wrote:
> On Sun, 7 May 2000 na...@dr... wrote:
> 
>> Ok I just looked at the dump from a netscape server. I'm not that
>> familiar with the LDAP3 spec but it should be perfectly valid to have a
>> read-only schema. Whether we generate it or just use an extract from
>> another server is not a big deal. My point being that an openldap 1.x
>> server could provide a schema to clients who want/need it (and if gq
>> wants it we can provide a solution for openldap users).
> 
> The schema code in GQ is entirely based on openldap-devel's excellent schema
> extensions to the V3 API spec. It seems like a lot of work to hack that into
> OpenLDAP 1.2.x, when a V3-capable OpenLDAP is just around the corner. I
> doubt if it would be accepted into the distribution.

Looking at the code, get_server_schema() just does a simple ldap_search
to the server and then uses some local functions (ldap_str2objectclass
and friends) to parse the info. That same info that was retrieved could
have come from an openldap 1.x server.

Yes, you do need an openldap 2.x client library to support it but you
could easily use an openldap 1.x server to provide the information.

-- 
Doug Nazar
Dragon Computer Consultants Inc.
Tel: (416) 708-1578     Fax: (416) 708-8081

On  7 May, Ross Golder wrote:
> Would patches that make GQ a GNOME application offend anyone?
> 
> For example, I'm thinking of converting the menu bar to a GNOME menu
> bar. As this would mean a new library dependency, I thought I best
> check.

For those of us not running gnome, what is a Gnome menu bar? What
advantages does it have?

-- 
Doug Nazar
Dragon Computer Consultants Inc.
Tel: (416) 708-1578     Fax: (416) 708-8081

> AFAICR, modrdn supports it directly but you can only change either the
> RDN or the suffix, not both. This means you'll need to perform at least
> two modrdns (three if there would be a clash on one of the operations).
> What I was thinking of with a popup as a radiobutton selecting a rename
> or move and an entryfield for the changed info. This could also be two
> different menu options.

My bad. I got confused with the LDAP v3 spec (RFC 2251) from when I was
writing the Ethereal LDAP dissector versus the C library (RFC 1823).

LDAP V3 protocol supports it, I have no idea how to do it from an
application <g> 

-- 
Doug Nazar
Dragon Computer Consultants Inc.
Tel: (416) 708-1578     Fax: (416) 708-8081