perl-ldap-dev

Re: is this error a code issue on my part or a bug with perl-ldap?

[Kent P. <kpe...@ev...>]

> I am attempting to use perl-ldap (both 0.25 and 0.251) to search and
display
> the results.  I working with perl 5.005_03 on a Solaris 8 box and perl
> 5.6.1, Activestate build 631 on a Win2K machine.  First, here is my code:

Alright, I screwed up my first post to the list.  The error I get, if I
actually give the script a search parameter, is:

[idev:/home/kperrier]$ ldap.pl cn=HelpDesk
Successful bind as
uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot.
Filehandle main::STDIN opened only for input at
/usr/perl5/site_perl/5.005/Net/LDAP/LDIF.pm line 397.
Filehandle main::STDIN opened only for input at
/usr/perl5/site_perl/5.005/Net/LDAP/LDIF.pm line 319.
Filehandle main::STDIN opened only for input at
/usr/perl5/site_perl/5.005/Net/LDAP/LDIF.pm line 288.
Filehandle main::STDIN opened only for input at
/usr/perl5/site_perl/5.005/Net/LDAP/LDIF.pm line 288.
Filehandle main::STDIN opened only for input at
/usr/perl5/site_perl/5.005/Net/LDAP/LDIF.pm line 288.
Filehandle main::STDIN opened only for input at
/usr/perl5/site_perl/5.005/Net/LDAP/LDIF.pm line 288.
Filehandle main::STDIN opened only for input at
/usr/perl5/site_perl/5.005/Net/LDAP/LDIF.pm line 288.
Filehandle main::STDIN opened only for input at
/usr/perl5/site_perl/5.005/Net/LDAP/LDIF.pm line 288.
Filehandle main::STDIN opened only for input at
/usr/perl5/site_perl/5.005/Net/LDAP/LDIF.pm line 288.
Filehandle main::STDIN opened only for input at
/usr/perl5/site_perl/5.005/Net/LDAP/LDIF.pm line 288.
Filehandle main::STDIN opened only for input at
/usr/perl5/site_perl/5.005/Net/LDAP/LDIF.pm line 288.
Filehandle main::STDIN opened only for input at
/usr/perl5/site_perl/5.005/Net/LDAP/LDIF.pm line 288.
Filehandle main::STDIN opened only for input at
/usr/perl5/site_perl/5.005/Net/LDAP/LDIF.pm line 288.
Filehandle main::STDIN opened only for input at
/usr/perl5/site_perl/5.005/Net/LDAP/LDIF.pm line 288.
Filehandle main::STDIN opened only for input at
/usr/perl5/site_perl/5.005/Net/LDAP/LDIF.pm line 288.
Filehandle main::STDIN opened only for input at
/usr/perl5/site_perl/5.005/Net/LDAP/LDIF.pm line 288.
Filehandle main::STDIN opened only for input at
/usr/perl5/site_perl/5.005/Net/LDAP/LDIF.pm line 288.
Filehandle main::STDIN opened only for input at
/usr/perl5/site_perl/5.005/Net/LDAP/LDIF.pm line 288.
Filehandle main::STDIN opened only for input at
/usr/perl5/site_perl/5.005/Net/LDAP/LDIF.pm line 288.
Filehandle main::STDIN opened only for input at
/usr/perl5/site_perl/5.005/Net/LDAP/LDIF.pm line 288.
Filehandle main::STDIN opened only for input at
/usr/perl5/site_perl/5.005/Net/LDAP/LDIF.pm line 288.
Filehandle main::STDIN opened only for input at
/usr/perl5/site_perl/5.005/Net/LDAP/LDIF.pm line 288.
Filehandle main::STDIN opened only for input at
/usr/perl5/site_perl/5.005/Net/LDAP/LDIF.pm line 288.
Filehandle main::STDIN opened only for input at
/usr/perl5/site_perl/5.005/Net/LDAP/LDIF.pm line 288.
Filehandle main::STDIN opened only for input at
/usr/perl5/site_perl/5.005/Net/LDAP/LDIF.pm line 288.
Filehandle main::STDIN opened only for input at
/usr/perl5/site_perl/5.005/Net/LDAP/LDIF.pm line 288.
Filehandle main::STDIN opened only for input at
/usr/perl5/site_perl/5.005/Net/LDAP/LDIF.pm line 288.
Done

Ok, now what am I doing wrong?

Kent

is this error a code issue on my part or a bug with perl-ldap?

[Kent P. <kpe...@ev...>]

I am attempting to use perl-ldap (both 0.25 and 0.251) to search and display
the results.  I working with perl 5.005_03 on a Solaris 8 box and perl
5.6.1, Activestate build 631 on a Win2K machine.  First, here is my code:

#!/usr/bin/perl -w

use Net::LDAP;
use Net::LDAP::LDIF;

my $server="idev.dobson.net";
my $port="18251";
my
$binddn="uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot";
my $passwd="admin";
my $basedn="o=dobson.net";
my $scope="sub";

my $c = Net::LDAP->new($server, port => $port) or
    die "Unable to connect to $server: $@\n";

$c->bind ($binddn, password => $passwd) or
    die "Unable to bind: $@\n";

if ($binddn eq "" && $passwd eq "") {
    print "Successful anonymous bind.\n";
} else {
    print "Successful bind as $binddn.\n";
}

my $searchobj = $c->search(base => $basedn, scope => $scope,
                           filter => $ARGV[0]);
die "Bad search, errorcode #".$searchobj->code() if $searchobj->code( );

# process the return values from search ( )
if ($searchobj) {
    my $ldif =  new Net::LDAP::LDIF("-");
    $ldif->write($searchobj->entries( ));
    $ldif->done( );
}

$c->unbind( );
print "Done\n"


On the Solaris box and the Win2K machine I get pretty much the same error.
On the Win2K machine I get:

Successful bind as
uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot.
Use of uninitialized value in substitution (s///) at
c:/Perl/site/lib/Net/LDAP/Filter.pm line 165.
Use of uninitialized value in substitution (s///) at
c:/Perl/site/lib/Net/LDAP/Filter.pm line 165.
Bad search, errorcode #89 at ldap.pl line 27.

on the Solaris box I get:

Successful bind as
uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot.
Use of uninitialized value at /usr/perl5/site_perl/5.005/Net/LDAP/Filter.pm
line 165.
Use of uninitialized value at /usr/perl5/site_perl/5.005/Net/LDAP/Filter.pm
line 165.
Bad search, errorcode #89 at ldap.pl line 27.

Is this a problem with my code or is it a problem with Net::LDAP?

Please, please help me out...

Kent

Re: Net::LDPS

[Paul L. <li...@so...>]

Thanks Chris,
 I used the Makefile that comes with Apache for generating certificates
and it cranked out a .pem file that does the trick. 
Paul

>>> Chris Ridd <chr...@me...> 06/11/02 01:14AM >>>
On 10/6/02 8:39 pm, Paul Lieberman <li...@so...> wrote:

> I'm trying to convert some scripts that used PerLDAP to Net::LDAP.
My
> server (Netware) requires an SSL conection with a client supplied
> certificate. In PerLDAP it worked like this ...
> 
>   $conn = new Mozilla::LDAP::Conn( host => 'myserver', port =>
'636',
> cert => 'cert7.db');
> 
> with Net::LDAPS I'm trying to do ...
> 
>   $conn = new Net::LDAPS( 'myserver', port => '636', clientcert =>
> 'cert7.db', clientkey => 'cert7.db');
> 
> and it dosn't work. I get no error, $conn just comes back undefined.
I
> can't remember how I originally generated 'cert7.db' but I'm
guessing
> its not the right format for Net::LDPS. So how do I make this work?

You got it! Both the cert and the key need to be PEM files. Also,
currently
the key needs to be unencrypted...

I think Netscape Communicator 4 stores certs in cert7.db and keys in
keys3.db, so you may be able to use the Netscape/Mozilla browser GUI
to
export your keypair to an (eg) PKCS#12 file. You can then use the
openssl
command line tools (openssl pkcs12 -help) to convert the PKCS#12 file
into a
cert and a key.

Cheers,

Chris


_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -
http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink 

Re: perl-ldap-dev digest, Vol 1 #589 - 8 msgs

[Bemtya J. <be...@ya...>]

I parsed a .ldif file as large as 3 Gigabytes and it's
okay.


__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

Re: StartTLS

[Chris R. <chr...@me...>]

Fabio Spataro <sp...@pr...> wrote:
> I have found a problem using start_tls in my perl script.
> 
> With IO::Socket::SSL 0.80 and Net::LDAP 0.251 start_tls failes on 
> reconnect. This is a well-known problem.
> 
> With IO::Socket::SSL 0.81 and Net::LDAP 0.251 start_tls failes in any 
> case (in my experience). I have modified Net/LDAP.pm in this way:
> 
> $ diff perl-ldap-0.251.old/lib/Net/LDAP.pm perl-ldap-0.251/lib/Net/LDAP.pm
> 805c805,806
> <   (IO::Socket::SSL::socketToSSL($sock) and tie *{$sock},
> 'IO::Socket::SSL', $sock) ---
>>  #(IO::Socket::SSL::socketToSSL($sock) and tie *{$sock},
>>  'IO::Socket::SSL', $sock) (IO::Socket::SSL::socketToSSL($sock) and tie
>>   *{$sock}, 'SSL_HANDLE', $sock)
> 
> Now start_tls is ok (on reconnect too).
> 
> Fabio Spataro

There's already a fix for that in version 1.31 of LDAP.pm in CVS, but I'm
not sure if that's made it out into a release yet.

Cheers,

Chris

StartTLS

[Fabio S. <sp...@pr...>]

I have found a problem using start_tls in my perl script.

With IO::Socket::SSL 0.80 and Net::LDAP 0.251 start_tls failes on 
reconnect. This is a well-known problem.

With IO::Socket::SSL 0.81 and Net::LDAP 0.251 start_tls failes in any 
case (in my experience). I have modified Net/LDAP.pm in this way:

$ diff perl-ldap-0.251.old/lib/Net/LDAP.pm perl-ldap-0.251/lib/Net/LDAP.pm
805c805,806
<   (IO::Socket::SSL::socketToSSL($sock) and tie *{$sock}, 'IO::Socket::SSL', $sock)
---
>  #(IO::Socket::SSL::socketToSSL($sock) and tie *{$sock}, 'IO::Socket::SSL', $sock)
>   (IO::Socket::SSL::socketToSSL($sock) and tie *{$sock}, 'SSL_HANDLE', $sock)

Now start_tls is ok (on reconnect too).

Fabio Spataro

Re: Net::LDAP & Kerberos?

[Booker C. B. <bb...@ne...>]

On Tue, 11 Jun 2002, Graham Barr wrote:

> On Tue, Jun 11, 2002 at 08:40:49AM +0100, Chris Ridd wrote:
> > On 10/6/02 11:11 pm, ma...@mj... <ma...@mj...> wrote:
> >
> > > Kerberos via LDAP should occur via SASL. I think some LDAP
> > > servers did native K4 before SASL.
> >
> > LDAPv2 had support for kerberos 4 in the bind operation. This support was
> > removed in LDAPv3, presumably with the expectation that you would want to do
> > it via a SASL mechanism instead. (Which makes sense.)
> >
> > Net::LDAP::ASN does not contain the ASN.1 for LDAPv2's kerberos 4 bind
> > choices any more, which explains the "not supported" claim :-)
>
> That is probbaly because when I changes to Convert::ASN1 I copied the ASN.1
> from the LDAPv3 RFCs. But ->bind still supports the krb4 parameters.
>
> We could add the krb4 entries into the ASN if someone wants to use them.
>

- The kerberos bind defined in ldapv2 should be deprecated from a
security standpoint. As far as I know the only server that currently
supports it is Openldap and it is marked as "deprecated". It is not
the optimum way to do kerberos, it is subject to a fairly trivial
replay attack. However from a practical standpoint,
I know that moving away from it can be difficult.

- I would encourage anyone pursuing new development to not use this
method, but instead to use one of the SASL methods. In particular,
kerberos 5, SASL/GSSAPI should be used instead of kerberos 4 when ever
possible.

- I think you should probably add the ASN entries back in, since most
ldap servers support both V2 and V3. IHMO, any new development using
these methods ( there are 2 k4 methods in the Umich code base) is
a mistake, but the module's job is to provide the rope, not to keep
you from putting it around your neck.

- Booker C. Bense

Re: ldap sorted question

[Roger B. <rj...@oc...>]

Graham,

Is this multivalued topic also related to the searchfilter you can pass
through?
ie.  filter => "(cn[1])",  as in my example?

You said it would be possible, so it isn't currently supported? If it
is, what's the right suffix, cos this surely isn't it...

If it isn't supported than I would surely rate this as a valueble
addition...

greetings,

Roger

Graham Barr wrote:
> 
> Currently the ->sorted method sorts using the order of values
> returned from the server. However it would be possible to support
> a suffix notation like you suggest.
> 
> Graham.
> 
> On Sun, Jun 23, 2002 at 02:03:31PM +0200, Roger Beulen wrote:
> > Hello,
> >
> > maybe this already has been answered before but I couldn't find it:
> >
> > when I use the  [ ATTR_LIST ] ) method, you can sort the results by the
> > attributes given in ATTR_LIST.
> >
> > We have a multivalued attribute CN consisting of:
> > Juan de Marco
> > Marco J, de
> > de Marco
> >
> > Is it possible that I want to have it sorted on the second value, Marco
> > J, de?
> > In a normal situation it would be sorted(cn) , but do I need to approach
> > it like an array in my case now? For example sorted(cn[1]) ?
> >
> > Any help would be welcome,
> >
> > greetings,
> >
> > Roger Beulen
> >
> >
> > _______________________________________________________________
> >
> > Don't miss the 2002 Sprint PCS Application Developer's Conference
> > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
> >
> 
> _______________________________________________________________
> 
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

Re: Net::LDPS

[Chris R. <chr...@me...>]

On 10/6/02 8:39 pm, Paul Lieberman <li...@so...> wrote:

> I'm trying to convert some scripts that used PerLDAP to Net::LDAP. My
> server (Netware) requires an SSL conection with a client supplied
> certificate. In PerLDAP it worked like this ...
> 
>   $conn = new Mozilla::LDAP::Conn( host => 'myserver', port => '636',
> cert => 'cert7.db');
> 
> with Net::LDAPS I'm trying to do ...
> 
>   $conn = new Net::LDAPS( 'myserver', port => '636', clientcert =>
> 'cert7.db', clientkey => 'cert7.db');
> 
> and it dosn't work. I get no error, $conn just comes back undefined. I
> can't remember how I originally generated 'cert7.db' but I'm guessing
> its not the right format for Net::LDPS. So how do I make this work?

You got it! Both the cert and the key need to be PEM files. Also, currently
the key needs to be unencrypted...

I think Netscape Communicator 4 stores certs in cert7.db and keys in
keys3.db, so you may be able to use the Netscape/Mozilla browser GUI to
export your keypair to an (eg) PKCS#12 file. You can then use the openssl
command line tools (openssl pkcs12 -help) to convert the PKCS#12 file into a
cert and a key.

Cheers,

Chris

Re: Net::LDAP & Kerberos?

[Graham B. <gb...@po...>]

On Tue, Jun 11, 2002 at 08:40:49AM +0100, Chris Ridd wrote:
> On 10/6/02 11:11 pm, ma...@mj... <ma...@mj...> wrote:
> 
> > Kerberos via LDAP should occur via SASL. I think some LDAP
> > servers did native K4 before SASL.
> 
> LDAPv2 had support for kerberos 4 in the bind operation. This support was
> removed in LDAPv3, presumably with the expectation that you would want to do
> it via a SASL mechanism instead. (Which makes sense.)
> 
> Net::LDAP::ASN does not contain the ASN.1 for LDAPv2's kerberos 4 bind
> choices any more, which explains the "not supported" claim :-)

That is probbaly because when I changes to Convert::ASN1 I copied the ASN.1
from the LDAPv3 RFCs. But ->bind still supports the krb4 parameters.

We could add the krb4 entries into the ASN if someone wants to use them.

Graham.

Re: Net::LDAP & Kerberos?

[Chris R. <chr...@me...>]

On 10/6/02 11:11 pm, ma...@mj... <ma...@mj...> wrote:

> Kerberos via LDAP should occur via SASL. I think some LDAP
> servers did native K4 before SASL.

LDAPv2 had support for kerberos 4 in the bind operation. This support was
removed in LDAPv3, presumably with the expectation that you would want to do
it via a SASL mechanism instead. (Which makes sense.)

Net::LDAP::ASN does not contain the ASN.1 for LDAPv2's kerberos 4 bind
choices any more, which explains the "not supported" claim :-)

> If your server supports SASL, the best route is to develop your own
> kerberos 4 SASL provider.
> 
> Mark

Nod.

Cheers,

Chris

Re: Net::LDAP & Kerberos?

[<ma...@mj...>]

Kerberos via LDAP should occur via SASL. I think some LDAP 
servers did native K4 before SASL.

If your server supports SASL, the best route is to develop your own 
kerberos 4 SASL provider. 

Mark


On 10 Jun 02, at 12:52, David Coulthart wrote:

> Looking through the documentation for Net::LDAP 0.25, it states that
> connecting via Kerberos4 is unsupported.  I'm assuming this means it
> won't work, not that it's just unsupported?  If this assumption is
> true, is there any work planned to add Kerberos4 support?  I am
> currently working on a project written in Perl that interfaces with an
> LDAP directory, but requires Kerberos support.  Our previous version
> uses Net-LDAPapi-1.43, but it seems there is a bug in that module
> which causes memory corruption of some sort when calling unbind() 
> (I've tried to pin it down, but I have no experience with XS & haven't
> had any success).  I would love to switch over to Net::LDAP since it
> seems to be the future of LDAP interaction with Perl, but w/o Kerberos
> support I'm stuck.  Can anyone provide any advice?
> 
> 
> Thanks,
> David Coulthart
> 
> _______________________________________________________________
> 
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -
> http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink
> 
> 
> 


Mark Wilcox
ma...@mj...
Got LDAP?

Net::LDPS

[Paul L. <li...@so...>]

I'm trying to convert some scripts that used PerLDAP to Net::LDAP. My
server (Netware) requires an SSL conection with a client supplied
certificate. In PerLDAP it worked like this ...

    $conn = new Mozilla::LDAP::Conn( host => 'myserver', port => '636',
cert => 'cert7.db');

with Net::LDAPS I'm trying to do ...

    $conn = new Net::LDAPS( 'myserver', port => '636', clientcert =>
'cert7.db', clientkey => 'cert7.db');

and it dosn't work. I get no error, $conn just comes back undefined. I
can't remember how I originally generated 'cert7.db' but I'm guessing
its not the right format for Net::LDPS. So how do I make this work?

Thanks,
Paul




--
Paul Lieberman                                     li...@so...
Systems Engineer                                 541-552-6962
Computing Services Center
Southern Oregon University
Ashland, OR

Net::LDAP & Kerberos?

[David C. <da...@co...>]

Looking through the documentation for Net::LDAP 0.25, it states that
connecting via Kerberos4 is unsupported.  I'm assuming this means it
won't work, not that it's just unsupported?  If this assumption is true,
is there any work planned to add Kerberos4 support?  I am currently
working on a project written in Perl that interfaces with an LDAP
directory, but requires Kerberos support.  Our previous version uses
Net-LDAPapi-1.43, but it seems there is a bug in that module which
causes memory corruption of some sort when calling unbind()  (I've tried
to pin it down, but I have no experience with XS & haven't had any
success).  I would love to switch over to Net::LDAP since it seems to be
the future of LDAP interaction with Perl, but w/o Kerberos support I'm
stuck.  Can anyone provide any advice?


Thanks,
David Coulthart

Re: Need your help

[Chris R. <chr...@me...>]

On 10/6/02 3:47 pm, Murugan K G <mur...@ya...> wrote:

> Hi 
>   I am getting the correct response name  while
> doing the following operation. But  i am not getting
> the proper response value.
> 
> How to decode the  message to get the proper response
> value. I am following the step as discussed with
> Graham.
> 
> $resname=Net::LDAP::Extension::response_name($extensionobj);
> $respcount=Net::LDAP::Extension::response($extensionobj);

What is $extensionobj? Specifically, what class of object is it?

If it is what I think it is (an instance of Net::LDAP::Extension) then you
should be doing this kind of thing instead:

    $resname = $extensionobj->response_name();

Cheers,

Chris

Need your help

[Murugan K G <mur...@ya...>]

Hi 
    I am getting the correct response name  while
doing the following operation. But  i am not getting
the proper response value.

How to decode the  message to get the proper response
value. I am following the step as discussed with
Graham.

$resname=Net::LDAP::Extension::response_name($extensionobj);
$respcount=Net::LDAP::Extension::response($extensionobj);

Any help ?

Regards
K.M


__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

Re: Application tag )=

[Murugan K G <mur...@ya...>]

Hi LDAP guru,
    I am really happy about your reply. Before sending
this query, i already tried with the following 

$responsename
=Net::LDAP::Extension::response_name($mesg);
$response=Net::LDAP::Extension::response
($mesg);

But i got correct Response name but some ascii
charecters ( some smiling faces like you ) for
response while printing  the results. Is it reqiured
to convert these values to Perl data types once again
using ASN1 module. Any help since i am very new to
this stuff.

Again, Thanks  for your help .

Regards
K.Murugan 


--- Graham Barr <gb...@po...> wrote:
> You do not need to decode this yourself. All you
> need are the ->response
> and ->response_name methods on the object returned
> by $ldap->extension
> 
> Graham.
> 
> On Mon, Jun 10, 2002 at 05:36:59AM -0700, Murugan K
> G wrote:
> > Hi
> >    Thanks for your previous response.  I have one
> more
> > problem while decoding the message returned from
> the
> > LDAP server.Is application [] tag is required
> while
> > decoding the  response as mentioned below.  Any
> help?
> > 
> > 
> > ##### decoding part ###########
> >  $asn = Convert::ASN1->new;
> > $asn->prepare(q<
> >  	    [APPLICATION 24] SEQUENCE {
> >  	      responseName OCTET STRING,
> >  	      identity OCTET STRING
> >  	    }
> >           );
> >         $out = $asn->decode($response); # which is
> >         #returned  by send message 
> >  	print "The identity value is ".
> >         $out->{identity};
> >  	print "The response Value is".
> >  $out->{responseName};
> >  
> >  Regards
> >  K.Murugan
> >  
> > 
> > 
> > __________________________________________________
> > Do You Yahoo!?
> > Yahoo! - Official partner of 2002 FIFA World Cup
> > http://fifaworldcup.yahoo.com
> 
>
_______________________________________________________________
> 
> Don't miss the 2002 Sprint PCS Application
> Developer's Conference
> August 25-28 in Las Vegas -
>
http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink
> 


__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

Re: Application tag )=

[Graham B. <gb...@po...>]

You do not need to decode this yourself. All you need are the ->response
and ->response_name methods on the object returned by $ldap->extension

Graham.

On Mon, Jun 10, 2002 at 05:36:59AM -0700, Murugan K G wrote:
> Hi
>    Thanks for your previous response.  I have one more
> problem while decoding the message returned from the
> LDAP server.Is application [] tag is required while
> decoding the  response as mentioned below.  Any help?
> 
> 
> ##### decoding part ###########
>  $asn = Convert::ASN1->new;
> $asn->prepare(q<
>  	    [APPLICATION 24] SEQUENCE {
>  	      responseName OCTET STRING,
>  	      identity OCTET STRING
>  	    }
>           );
>         $out = $asn->decode($response); # which is
>         #returned  by send message 
>  	print "The identity value is ".
>         $out->{identity};
>  	print "The response Value is".
>  $out->{responseName};
>  
>  Regards
>  K.Murugan
>  
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Yahoo! - Official partner of 2002 FIFA World Cup
> http://fifaworldcup.yahoo.com

Application tag )=

[Murugan K G <mur...@ya...>]

Hi
   Thanks for your previous response.  I have one more
problem while decoding the message returned from the
LDAP server.Is application [] tag is required while
decoding the  response as mentioned below.  Any help?


##### decoding part ###########
 $asn = Convert::ASN1->new;
$asn->prepare(q<
 	    [APPLICATION 24] SEQUENCE {
 	      responseName OCTET STRING,
 	      identity OCTET STRING
 	    }
          );
        $out = $asn->decode($response); # which is
        #returned  by send message 
 	print "The identity value is ".
        $out->{identity};
 	print "The response Value is".
 $out->{responseName};
 
 Regards
 K.Murugan
 


__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

Re: Could not decode LDAP extension packet - error

[Murugan K G <mur...@ya...>]

--- Graham Barr <gb...@po...> wrote:
> Please keep ldap communication on the ldap list
> 
> Graham.
> 
> On Mon, Jun 10, 2002 at 04:38:37AM -0700, Murugan K
> G wrote:
> > Hi
> >    Thanks for your help . That is working for me
> now.
> > I have one more problem  in decoding the  response
> > message  returned from the LDAP server.  Is
> > application [] tag is required while decoding  the
> > response as mentioned below.  

Regards
K.Murugan
> > 
> > ##### decoding part ###########
> > 
> > $asn = Convert::ASN1->new;
> > 	$asn->prepare(q<
> > 	    [APPLICATION 24] SEQUENCE {
> > 	      responseName OCTET STRING,
> > 	      identity OCTET STRING
> > 	    }
> >   >);
> > 	$out = $asn->decode($response); # which is
> returned
> > by send message 
> > 	print "The identity value is ". $out->{identity};
> > 	print "The response Value is".
> $out->{responseName};
> > 
> > Regards
> > K.Murugan
> > 
> > 
> > 
> > 
> > --- Graham Barr <gb...@po...> wrote:
> > > You dont need the APPLICATION 23 in your code,
> try
> > > 
> > >  $asn = Convert::ASN1->new;
> > >  $asn->prepare(q<
> > >        flags INTEGER,
> > >        dn    OCTET STRING
> > >      >);
> > >  
> > >  $pdu = $asn->encode( flags => 0, dn =>
> > > "ou=test,o=cdac");
> > >  $ldap->extension(
> > >     name => '2.16.840.1.113719.1.27.100.3',
> > >     value => $pdu
> > >  );
> > > 
> > > Graham.
> > 
> > 
> > __________________________________________________
> > Do You Yahoo!?
> > Yahoo! - Official partner of 2002 FIFA World Cup
> > http://fifaworldcup.yahoo.com


__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

[Fwd] practical limits on LDIF

[Graham B. <gb...@po...>]

----- Forwarded message from Abhijeet <abh...@en...> -----

Date: Fri, 07 Jun 2002 16:44:07 -0700
To: gb...@po...
From: Abhijeet <abh...@en...>
Subject: practical limits on LDIF

Hi,

What was the biggest file that you have heard of being parsed 
with the ldif class?  Do you think there is a limit or should it 
scale to several 100 [~400MB] ?

thanks,
abhijeet.

----- End forwarded message -----

limitation on size?

[Bemtya J. <be...@ya...>]

Hi,

Has anybody hit any limitations on the size of an LDIF
that can be parsed using the LDIF class?

thanks,
bemtya.

__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

Re: Could not decode LDAP extension packet - error

[Graham B. <gb...@po...>]

You dont need the APPLICATION 23 in your code, try

 $asn = Convert::ASN1->new;
 $asn->prepare(q<
       flags INTEGER,
       dn    OCTET STRING
     >);
 
 $pdu = $asn->encode( flags => 0, dn => "ou=test,o=cdac");
 $ldap->extension(
    name => '2.16.840.1.113719.1.27.100.3',
    value => $pdu
 );

Graham.

On Thu, Jun 06, 2002 at 06:32:34AM -0700, Murugan K G wrote:
> Hi
>    Thanks for your comment. Basically i wanted to 
> create a new  partition  using  Net::LDAP::Extension 
> in eDirectory
> ##################################################
> The requestValue has the following format:
> requestValue ::=
>      flags      INTEGER
>      dn         LDAPDN
> #####################################################
> I am getting "could not decode LDAP extension packet"
> error message when i used  the following encoding
> procedure.  Is it the rights way  to encode the
> message for the above mentioned extension?. I am sure
> about the OID.
> 
> Thanks in advance.
> 
> $asn = Convert::ASN1->new;
> $asn->prepare(q<
>       [APPLICATION 23] SEQUENCE {
>       flags INTEGER,
>       dn    OCTET STRING
>     }>);
> 
> $pdu = $asn->encode( flags => 0, dn =>
> "ou=test,o=cdac");
> 
> 
> $mesg->encode
> 	( 
>        	 extendedReq =>{
>          requestName =>
> '2.16.840.1.113719.1.27.100.3',
> 	 requestValue => $pdu
> 	 }
>         )or die "Not able to encode the extended
> values\n";
> 
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Yahoo! - Official partner of 2002 FIFA World Cup
> http://fifaworldcup.yahoo.com

Re: Could not decode LDAP extension packet - error

[Murugan K G <mur...@ya...>]

Hi
   Thanks for your comment. Basically i wanted to 
create a new  partition  using  Net::LDAP::Extension 
in eDirectory
##################################################
The requestValue has the following format:
requestValue ::=
     flags      INTEGER
     dn         LDAPDN
#####################################################
I am getting "could not decode LDAP extension packet"
error message when i used  the following encoding
procedure.  Is it the rights way  to encode the
message for the above mentioned extension?. I am sure
about the OID.

Thanks in advance.

$asn = Convert::ASN1->new;
$asn->prepare(q<
      [APPLICATION 23] SEQUENCE {
      flags INTEGER,
      dn    OCTET STRING
    }>);

$pdu = $asn->encode( flags => 0, dn =>
"ou=test,o=cdac");


$mesg->encode
	( 
       	 extendedReq =>{
         requestName =>
'2.16.840.1.113719.1.27.100.3',
	 requestValue => $pdu
	 }
        )or die "Not able to encode the extended
values\n";



__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

Re: Could not decode LDAP extension packet - error

[Graham B. <gb...@po...>]

On Thu, Jun 06, 2002 at 05:31:08AM -0700, Murugan K G wrote:
> Hi 
>    I may be asking very simple question since  i am
> very new to LDAP stuff. Thanks for your answers. 
> I am getting "Could not decode LDAP extension packet"
> error messasge.
>  May be i am sending wrong encoded message from the
> client as  below.   Any ideas?. 

Perhaps it would help if you described what you are trying todo
and not just ask "what is wrong with this code"

Graham.

> 
> Any help mostly welcome.
> 
> Thanks in advance.
> 
> Regards
> K.Murugan
> 
> my $mesg = $ldap->message('Net::LDAP::Extension' =>
> $arg);
> 
> $ldap->start_tls();
> 
> $asn = Convert::ASN1->new;
> $asn->prepare(q<
>       [APPLICATION 23] SEQUENCE {
>       flags INTEGER,
>       dn    LDAPDN
>     }>);
> 
> $pdu = $asn->encode( flags => 0, dn =>
> "ou=test,o=xxxx");
> 
> $out = $asn->decode($pdu);
> print $out->{flags}," ",$out->{dn},"\n";
> 
> 
> $mesg->encode
> 	( 
>        	 extendedReq =>{
>          requestName =>
> '2.16.840.1.113719.1.27.100.3',
> #####################################
> 	 requestValue => $pdu
> #######################################
> 	 }
>         )or die "Not able to encode the extended
> values\n";
> 
> 	$response=$ldap->_sendmesg($mesg) or die "Not  able
> to send message\n";
> 	$mesg->sync(); 
> 
>         if( $mesg->code ne LDAP_SUCCESS)
>         {
> 	   	print "LDAP ERROR\n		";
> 	        print "The response name is ".
> $response->{responseName};
> 	        $ldap->unbind();
>         }
>         else
>         {
> 		print "The response name is ".
> $response->{responseName};
> 	        $ldap->unbind();	
> 	}
> 	print "Ldap extension operation result",      
> ldap_error_name($mesg->code),"\n";
> 	print $mesg->error;
> 
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Yahoo! - Official partner of 2002 FIFA World Cup
> http://fifaworldcup.yahoo.com
> 
> _______________________________________________________________
> 
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
>