sion OIDs
* Constant.pm: add references to perl-ldap's modules
Bug Fixes
* META.json: update author & bugtracker
* Control/*.pm: typo & grammar fixes
* Control/Relax.pm: slight rephrasing
* FAQ.pod: fix spelling/grammar error
* Changes: fix typo
--
Peter Marschall
pe...@adpm.de
ersist the default sslserver
* LDAP.pm: correct parameter to restrict IP family with IO::Socket::IP
* data/regenerate_cert.sh: fix shebang
--
Peter Marschall
pe...@adpm.de
to.
Was able to reproduce it on a working installation of perl-ldap:
$ perl -MNet::LDAP -e 'my $ld = Net::LDAP->new("ldaps://unknown") or die($@);'
Name or service not known at -e line 1, line 755.
Maybe a typo in the URL?
Best
PEter
--
Peter Marschall
pe...@adpm.de
Hi all,
I just released perl-ldap 0.66 to CPAN:
http://search.cpan.org/dist/perl-ldap/
https://metacpan.org/release/perl-ldap
For those of you directly pulling from GitHub, the repository
https://github.com/perl-ldap/perl-ldap/releases
has been updated accordingly.
Please
:eDirectory
If you provide code that is reasonably generic (and does not only fulfill your
specific use case), I may consider including it. (No guarantee)
Best
PEter
--
Peter Marschall
pe...@adpm.de
is
78.
Setting it to 40 or lower inhibits wrapping.
Best
Peter
--
Peter Marschall
This method supports everything you need with an appropriately opened LDIF
object
* The changes in https://github.com/marschap/perl-ldap/tree/next
I expect this to become the next perl-ldap release.
Please test the changes in Net::LDAP::Entry.
Improvement ideas welcome.
Especially if they hinder the user from making stupid mistakes like calling
LDIF(version=>1)
Peter
--
Peter Marschall
e check them give them a shake and report bugs, improvements, ...
and of course also, what you want to see in future versions of perl-ldap.
Best
PEter
--
Peter Marschall
pe...@adpm.de
Hi,
Am Donnerstag, 28. Dezember 2017, 13:58:10 CET schrieb Zeus Panchenko:
> Peter Marschall wrote:
> > Have you tried patching
> > usr/local/lib/perl5/site_perl/Convert/ASN1/_decode.pm?
Digging a bit deeper, I don't think Convert::ASN1 is the issue.
The issue is indeed in
do yourself a favour and update to a recent version.
While not directly fulfilling your request, the newer versions have an
extended Net::LDAP::Entry->update() method, that allows using an LDIF file as
a target to write to.
Best regards
PEter
--
Peter Marschall
pe...@adpm.de
l
> after setting dds-max-ttl to some big enough value, same code works well
Do I get it right, that only the error case (i.e. setting the ttl to a higher
value than allowed) fails, while the correct case (setting the ttl to a value
within the bounds allowed) works?
In any case, can you p
code('UTF-8' ,$_) for @ARGV;
should be sufficient.
You may also have a look at the 'utf8::all' package that does a lot of the
above for you automatically.
Please read the perlunicode manual page for more detailed information.
Best
PEter
--
Peter Marschall
pe...@adpm.de
ithub.com/marschap/perl-ldap/commit/cd7602113d1971d3bfc7681e3c7869a5a1ce70ae
This commit updates schema2ad's POD documentation slightly
You can read it using e.g 'pod2text schema2ad.pl'
Please test and reprot feedback to the mailing list
Best
Peter
--
Peter Marschall
pe...@adpm.de
/releases
has been updated accordingly.
Please find a short log of all the changes below.
Thanks to
* Troy Loveday
for his bug report / patch.
--
Peter Marschall
pe...@adpm.de
0.65 -- Mon Apr 6 19:43:37 CEST 2015
Enhancements:
* t/74matchedvalues.t: more tests
* {ASN,Extension}.pm: update
ndex-*" : 'member' ]
Thanks for reporting the issue.
The fix will be in the next release of perl-ldap.
Best
Peter
--
Peter Marschall
pe...@adpm.de
.
Please find a short log of all the changes below.
Thanks to
* Thomas Guevin
* Jim Toth
* Jitka Plesnikova
for their bug reports / patches.
Enjoy the new release!
Peter
--
Peter Marschall
pe...@adpm.de
0.64 -- Thu Jun 19 17:48:08 CEST 2014
Bug Fixes:
* LDAP.pm: set SSL_cipher_list correctly
* RT
$arg->{capath} ? $arg->{capath} : '',
> SSL_key_file=> $clientcert ? $clientkey : undef,
>
>
> Please address in 0.64 if possible.
Patched in private repo.
Will be included in 0.64.
Thanks
--
Peter Marschall
pe...@adpm.de
gt; [...]
>
> When I include the "$cur_entry->changetype(modify);" line, the script
> returns:
>
> No attributes to update at ./ldap-update.pl line 23, line 751.
Net::LDAP::Entry's changetype() method clears all previous changes when called
with an argument.
Solution is simple: set the changetype first.
Best
Peter
--
Peter Marschall
pe...@adpm.de
anges below.
The most noteworthy ones are IMHO:
* use default cyphers of the underlying SSL library
instead of setting SSL_ciphers to ALL by default
* write controls to LDIF files (more complete RFC support)
Thanks to
* Petr Písař
* Hanno Hecker
for their contributions
Best
Peter
--
Peter Mars
t::INET6
when the former one is installed.
If IO::Socket::IP does not suffer the problems that recent versions
of IO::Socket::INET6 seem to have in Windows, then everything should
work as before including IPv6 support.
Best
PEter
--
Peter Marschall
pe...@adpm.de
gain
--
Peter Marschall
pe...@adpm.de
til.pm: fix corner cases in time conversion functions
Best
Peter
--
Peter Marschall
pe...@adpm.de
x27;t installed
- this solves RT#93122, which IMHO is not really a bug of perl-ldap
* remove trailing whitespace in contrib/*
--
Peter Marschall
pe...@adpm.de
Hi,
On Wednesday, 5. March 2014 11:32:52 Paul LeoNerd Evans wrote:
> On Wed, 05 Mar 2014 11:31:29 +0100 Peter Marschall wrote:
> > Paul,
> > from the mail above, I get it that Timeout is working in
> > IO::Socket::IP. Can you confirm?
> > Additionally, may I as
Hi,
On Wednesday, 5. March 2014 10:17:12 Michiel Beijen wrote:
> On Tue, Mar 4, 2014 at 7:56 PM, Peter Marschall wrote:
> > But there's a downside too:
> > With IO::Socket::IP, the option Timeout to Net::LDAP->new() will be
> > ignored.
> I asked Paul (cc) ab
IO::Socket::INET6
What's your opinion?
Best
PEter
--
Peter Marschall
pe...@adpm.de
- simplify _write_entry
- coding style harmonization
- error checks when reading changetype: delete
- make _error() return undef/empty list, adapt callers
- refactor handling DNs when reading
- new method _read_attribute_value()
--
Peter Marschall
pe...@adpm.de
ext::Soundex for tests
--
Peter Marschall
pe...@adpm.de
f more grammar & spelling fixes / harmonizations
Enhancements:
* LDAP.pm: use data_ready() in process()
* Util.pm: simplify return on error
* Constant.pm: add constant LDAP_CONTROL_NOOP
* Schema.pm: call isa() as recommented in UNIVERSAL.pm
--
Peter Marschall
pe...@adpm.de
aver
- convert _write_... to object methods
- use indirect file handles for URLs
* LWP/Protocol/ldap.pm: use regex as 1st arg to split()
--
Peter Marschall
pe...@adpm.de
ively impact your patch? Which one should then prevail?
Did you at least report the bug to IBM?
Because their non-standards compliant tool is the cause of the whole
discussion.
Best
Peter
--
Peter Marschall
pe...@adpm.de
ir tool (even if they
> >might not react). Maybe they are not even aware of the issue.
>
> If I put the bug report in, will you incorporate the patch? :)
No. [I do not want perl-ldap to look like the easier target ;-]]
My hope is IBM will fix their bug and adhere to well-established standards.
If they do, you can throw away the preprocessor step.
Best
PEter
--
Peter Marschall
pe...@adpm.de
p -vi ^control: > RFC-CONFORMING-FILE
[the first command is required to unwrap the wrapped lines]
Alternatively you may add a
changetype: add line
after each unwrapped dn: line.
> >Instead, please get the dump utility fixed so that it adheres to the RFC.
>
> I don't
Instead, please get the dump utility fixed so that it adheres to the RFC.
Best
Peter
PS: Please don't top-post
--
Peter Marschall
pe...@adpm.de
pm: add LDAP_CONTROL_RELAX
LDAP.pod: omit space from filter in synopsis
FAQ.pod: don't talk of "2 lines" when there's only one
Extra/eDirectory.pm: fix typo, space police
--
Peter Marschall
pe...@adpm.de
ities.
Net::LDAP exposes the socket it uses via the socket() method.
Can't this be used to implement the things on the application side?
Best
PEter
--
Peter Marschall
pe...@adpm.de
partially support controls when reading
* Util.pm: add time conversion functions
* Makefile.PL: update recommends, add comments on core modules
* FAQ.pod: update info on required/optional modules
* LDAP.pod,FAQ.pod: harmonize documentation of scope values
--
Peter Marschall
pe...@adpm.de
Hi Quanah,
On Monday, 28. January 2013, Quanah Gibson-Mount wrote:
> Just to note, the "Download" link on the top right hand side of the page
> has been pointing to the wrong release for a while. It still points to
> 0.49.
Fixed
Thanks for the heads-up
Peter
--
Peter Marschall
pe...@adpm.de
l.pm: new function ldap_url_parse()
* RT#77716: LDAP.pm: new option keepalive for new()
* LDAP.pm: convert scheme to lowercase in new()
* FAQ.pod: how to search all members of a large AD group
* FAQ.pod: how to do nested group searches in AD
--
Peter Marschall
pe...@adpm.de
use IPv6".
This is reflected in the documentation.
I see two options for amavis to fix it:
* raise the required perl-ldap version to 0.46 and remvoe "inet6 => 1"
from the constructor fo theNet::LDAP object
* make the addition of inet6 => 1 dependent on perl-ldap's version
Best
PEter
--
Peter Marschall
pe...@adpm.de
ficates, CRLs, JPEG photos, ... .
This also applies to GUID values from AD.
For most of those attribute typess there are Perl modules available that do a
really good job.
Did you check with CPAN?
http://search.cpan.org/search?query=GUID
If none of them suits your needs, you can always take the code you found on
the web.
Best
Peter
--
Peter Marschall
pe...@adpm.de
is the correct
> interpretation?
A short script gives the answer: it is zero-based.
A fix of the Net::LDAP::Search man page will be in the next release.
Best
Peter
--
Peter Marschall
pe...@adpm.de
GitHub repository has been updated too.
Enjoy
Peter
--
Peter Marschall
pe...@adpm.de
0.52 -- Tue Jan 1 13:54:22 CET 2013
Bug Fixes:
* fix PreRead & PostRead controls
* AD.pm: fix typo in documentation
Enhancements:
* add tests for PreRead & PostRead controls
* FAQ.pm: exa
t reproduce the issue with Strawberry Perl
5.16.2.1 (with Socket 2.006) when connecting to a non-AD LDAP server.
So:
* Can you try reproding the issue using another LDAP server (preferably
another type. i.e. no AD)?
* Can you try reproducing the issue using the above version of Strawberry Perl
(http://strawberryperl.com/)?
* Can you double check your implementation?
I assume you did it for yourself, and did not use pre-compiled images from
somewhere on the net?
Please report back.
Thanks
PEter
--
Peter Marschall
pe...@adpm.de
Hi,
On Friday, 21. December 2012, Girish Jagdish Khetan wrote:
> We have used Net::LDAP in Perl (Version: 5.6.1) to process data from LDAPv3
> server on Linux environment. We are using callback (Asynchronous
> processing) to process the data. At runtime, scripts are failing abruptly
> with I/O Err
filters.
Of course, the GitHub repository https://github.com/perl-ldap/perl-ldap
has been updated accordingly.
Enjoy
Peter
--
Peter Marschall
pe...@adpm.de
0.51 -- Sat Dec 1 14:37:35 CET 2012
Bug Fixes:
* RT#81380: in Filter.pm unescape hexpairs and ( ) \ * only
* tests: compare files in "
ourse, the GitHub repository https://github.com/perl-ldap/perl-ldap
has been updated accordingly.
Enjoy
Peter
--
Peter Marschall
pe...@adpm.de
0.50 -- Sat Nov 24 13:03:45 CET 2012
Bug Fixes:
* t/07filtermatch.t: use core module Text::Soundex instead of String::Approx
* Message.pm: fix regression
eorganize servers tests: rename t/5X*.t -> t/4(X+1)*.t
- t/47ipc.t: add TLS tests
- t/60cancel.t: new, tests for Net::LDAP::Extension::Cancel
- t/70sortctrl.t: make it a server test & add multi-attribute testcase
--
Peter Marschall
pe...@adpm.de
75166b9db97a8c97e20281490e491a
In my (short & preliminary) tests the patch fixed the issue.
Please report whether it does the trick for you too.
Best
Peter
--
Peter Marschall
pe...@adpm.de
/perl-ldap
has been updated accordingly.
Enjoy
Peter
--
Peter Marschall
pe...@adpm.de
0.49 -- Sat Oct 5 10:00:30 CEST 2012
Bug Fixes:
* RT#79763 extend ldap_explode_dn() for RFC 4514
* RT#77291 canonicalize host name with ldapi://
* LDAP.pm: don't try to set errors on undefined ob
tive
Con's:
- might accept DN's that are not conforming to any of the RFCs
(but canonical_dn will make them confiorming to both)
Which of the alternatives do you prefer?
Best
PEter
--
Peter Marschall
pe...@adpm.de
Hi Quanah,
On Thursday, 20. September 2012, Quanah Gibson-Mount wrote:
> --On Thursday, September 20, 2012 9:34 AM +0200 Peter Marschall
> >
> > Feedback is very welcome
>
> Thanks Peter! Should I look at this or perl-ldap 0.48? ;)
At this _and_ perl-ldap 0.48 ;-)
These
cent OpenLDAP
* removed trailing spaces
* support OpenLDAP extension: scope => "children"
--
Peter Marschall
pe...@adpm.de
updated yet)
Another issue was found in escape_dn_value() which got fixed in
https://github.com/marschap/perl-
ldap/commit/11ea6b176a0e728d10cc3219cbb84fd8018df5a6
Feedback is very welcome
Best regards
Peter
--
Peter Marschall
pe...@adpm.de
dapi:// URIs with LWP
* contrib/LWPsearch.pl: demo program for LWP::Protocol::ldap*
* update link list in the FAQ
* update references to RFCs
--
Peter Marschall
pe...@adpm.de
tandardized,
but widely used, SSL-encrypted connection to port 636
My recommendation:
1) Net::LDAP + start_tls
2) Net::LDAPS [of 1) is not supproted by the server]
3) Net::LDAP without TLS only for anonymous access
Best
Peter
--
Peter Marschall
pe...@adpm.de
date URLs a bit more
--
Peter Marschall
pe...@adpm.de
ypo fixes in documentation
Enhancements
* RT#77458 re-work IPv6 support
* Don't accumulate intermediate messages passed to a callback.
* slightly extend Net::LDAP::Entry->update() and document it
* convenience alias done() for Net::LDAP->unbind()
--
Peter Marschall
pe...@adpm.de
it may
be set, and then use this value.
As a side note:
If I remember the RFC correctly, Boolen attributes are a bit special, as the
false value is given implicitly, i.e. by the absence of the attribute.
[might not apply to ADAM & Co - I've seen other LDAP servers that allowed
booeanAttribute=FALSE too]
Best
PEter
--
Peter Marschall
pe...@adpm.de
On Sunday, 22. April 2012, Alexei Znamensky wrote:
> Hi Peter,
>
> On 22 April 2012 15:10, Peter Marschall wrote:
> > [...]
>
> In that case, why does Net::LDAP::Filter constructor accepts such filters
> as argument? Shouldn't it moan that this is illegal? It b
al filters.
> [...]
> Am I missing something here?
The filters using DN would fail on a standard LDAP server too.
Net::LDAP::FilterMatch behaves correctly.
Best
PEter
--
Peter Marschall
pe...@adpm.de
t; Anyway, long story short, by backgrading IO::Socket::SSL to v1.06, the
> issue seems to go away, as these sort of checks are not performed at all
> in older versions of the module.
>
> Cheers,
>
> -Matt
>
>
>
> IMPORTANT: This email remains the property of the Department of Defence
> and is subject to the jurisdiction of section 70 of the Crimes Act 1914.
> If you have received this email in error, you are requested to contact
> the sender and delete the email.
--
Peter Marschall
pe...@adpm.de
oc updates then and with this update and the
new controls & extensions, shouldn't this make a nice new 0.44?
Best
Peter
--
Peter Marschall
pe...@adpm.de
Hi,
On Thursday, 8. September 2011, Graham Barr wrote:
> On Sep 7, 2011, at 09:26 , Peter Marschall wrote:
> > * 0.43 has a serious regression: commit 041d540 broke start_tls
> > completely
> >
> > and led to warnings being generated at every encrypted connectio
x that or is that another problem?
A) Please keep your mail on the list!
B) Please do not top-post!
C) To answer your question:
These fixes are completely unrelated to the problem you have.
Hint: compare the dates of your issues and when the regresion
was introduced.
Peter
n
* extended documentation for Pre-Read & Post-Read controls
As bonus:
* Assertion Control implemented
* new control LDAP_CONTROL_PERMISSIVEMODIFY
Thanks
Peter
--
Peter Marschall
pe...@adpm.de
shown in the schema, but as this is non-
standard, the results depend in the specific implementation (e.g. lexical
instead of numerical sorting, ...)
--
Peter Marschall
pe...@adpm.de
uot;available" & "explicitly" ;-)
Best regards
Peter
--
Peter Marschall
pe...@adpm.de
escape_dn_value()
* unescape_dn_value()
Best regards
Peter
--
Peter Marschall
pe...@adpm.de
Hi,
On Tuesday, 29. March 2011, Marc Lehmann wrote:
> al rule, in perl, when you use a global variable, you should save
> and restore it (map, for
This is already fixed in perl-ldap's repository at
git://github.com/gbarr/perl-ldap.git
Thanks
Peter
--
Peter Marschall
pe...@adpm.de
Hi,
the attached patch fixes a few typos in Net::LDAP::Entry.pod
Please consider it for inclusion into the next version of perl-ldap.
Best
Peter
--
Peter Marschall
pe...@adpm.de
From fb4418175d436e598e72e4a2fc7d185a40c8e378 Mon Sep 17 00:00:00 2001
From: Peter Marschall
Date: Fri, 2 Jul 2010
eter too.
It would be great if this patch would make it into the next release
of perl-ldap.
Best regards
Peter
--
Peter Marschall
pe...@adpm.de
From bce3842056339ebdbbaaebd46857b13eadc68759 Mon Sep 17 00:00:00 2001
From: Peter Marschall
Date: Sun, 9 Jan 2011 19:47:55 +0100
Subject: [PATCH] exte
gt; $2); # for adding and updating
> $entry->add(...);
> $entry->update($ldap);
Personally I do not consider this approach a safe one.
Regards
Peter
--
Peter Marschall
pe...@adpm.de
nt-in-_-cis-exact-_.patch
the issue at hand
* 0004-FilterMatch.pm-correct-of-args-in-function-declar.patch
fix # of args in function declarations/definitions
Please add them to your repo.
Thanks in advance
Peter
--
Peter Marschall
pe...@adpm.de
From 64194a7d46cc5dd665678346c42e80a2918eae3
why. The
> only reason why
The reason for the failure is easy to see, once you decode the base64-encoded
DN in your example:
Кацубо Владимир,cn=persons,cn=centurion
This is simply no legal DN (Hint: it lacks the attribute name in the RDN).
Regards
Peter
--
Peter Marschall
pe...@adpm.de
ter Marschall
[EMAIL PROTECTED]
From 1ff0c69e9f5f7256ea7bce031abb2a7a52c83893 Mon Sep 17 00:00:00 2001
From: Peter Marschall <[EMAIL PROTECTED]>
Date: Fri, 19 Sep 2008 18:51:16 +0200
Subject: [PATCH] use "resultCode" instead of incorrect "Code" (found by Daniel Stutz)
---
lib
>
> [...]
>
> was added just after the loop. I judged this unnecessary because I'm using
> the 'die' method on error. But I may be wrong...
>
> Anyway, any help would be greatly appreciated.
I did not look at the code, but did you try to check
- using Net::LDAP's debug method/option
- with a network sniffer
to see in more detail what's going on?
Maybe it's the server not responding.
Regards
Peter
--
Peter Marschall
[EMAIL PROTECTED]
hen opening a 2nd connection, you continue to work with the
"function" account from step on in the $ldap session, that
may have special permissions.
When re-binding in the same session, you work with the
LDAP permissions of the user logging in to the web page.
This may or may not be whatyou want.
3) Check if binding succeeded and continue as needed.
Don't try to compare passwords using ldap-compare.
This will most probably not work as passwords are either
encrypted on the server or cannot be compared using LDAP's
compare method.
This is highly dpenedant on the implementation of the server
and precludes other authentication metods than plain simple
username/password authentication.
Hope it helps
Peter
--
Peter Marschall
[EMAIL PROTECTED]
.
For you convenience I also append it to this posting.
Please test and report back.
CU
PEter
--
Peter Marschall
[EMAIL PROTECTED]
--- Constant.pm (revision 549)
+++ Constant.pm (working copy)
@@ -135,60 +135,32 @@
Operation completed without error
-=item LDAP_PP_PASSWORD_EXPIRED (0)
-
-T
t; character not before but after each entry. This produces the same
> > output as by ldapsearch and will be accepted by the perl backend from
> > OpenLDAP.
>
> Anyone see any issue with doing this?
I don't think this should hurt.
(Don't forget to add an \n to the version line as well)
CU
Peter
--
Peter Marschall
[EMAIL PROTECTED]
quainted wit git.
Will this change also affect the other modules Auth::SASL,
Convert::ASN1, ...?
Peter
--
Peter Marschall
[EMAIL PROTECTED]
;= $len or $len <= 40;
use integer;
my $l2 = $len-1;
my $x = (length($_[0]) - $len) / $l2;
Hope it helps
Peter
--
Peter Marschall
[EMAIL PROTECTED]
ot;;
'192.168.1.18 192.168.1.12' is not an array reference but a string.
Please try it with
[ qw(192.168.1.18 192.168.1.12) ]
or the equivalent
[ '192.168.1.18', '192.168.1.12' ]
as the 1st arg to Net::LDAP->new()
Hope it helps
Peter
--
Peter Marschall
[EMAIL PROTECTED]
erver supports LDAPI connections, i.e. LDAP over Unix domain
sockets (as e.g. OpenLDAP does), you may use ldapi:// style URLs.
See Net::LDAP(3pm) for details.
Hope this helps
Peter
--
Peter Marschall
[EMAIL PROTECTED]
callbacks.
See CALLBACKS in the man pages for that.
Regards
Peter
--
Peter Marschall
[EMAIL PROTECTED]
ber' => 'cn=user');
> $ldif->write_entry($group);
>
> Results in
>
> dn: cn=group
> changetype: add
>
> dn: cn=group
> changetype: add
> member: cn=user
>
> Whereas I'd want something as :
>
> dn: cn=group
> changetype: add
>
> dn: cn=group
> changetype: modify
> replace: member
> member: cn=user
Hope it helps
Peter
--
Peter Marschall
[EMAIL PROTECTED]
n;
> use integer;
> my $l2 = $len-1;
> my $x = (length($_[0]) - $len) / $l2;
> my $extra = (length($_[0]) == ($l2 * $x + $len)) ? "" : "a*";
> join("\n ",unpack("a$len" . "a$l2" x $x . $extra,$_[0]));
> }
Thanks for thebug report.
I fixed it in perl-ldap's SVN repository with a similar patch.
CU
Peter
--
Peter Marschall
[EMAIL PROTECTED]
ng the 'raw' option to the constructor, passing it a regex of
> attribute types you don't want to convert. See the docs for details
> and a little example.
Just to avoid misunderstandings:
When the raw option is not given, Net::LDAP's behaviour is unchanged.
Only when raw => REGEX is given, all attributes not matching the regex are
converted to Perl-Unicode strings
Regrds
Peter
--
Peter Marschall
[EMAIL PROTECTED]
Iam not 100% sure what it indicates exactly. but I
guess it has problems resolving the hostname of the server.
Peter
--
Peter Marschall
[EMAIL PROTECTED]
committed to SVN.
(although it was not really a bug as the doc states to use array refs ;-)
Thanks for spotting it
Peter
--
Peter Marschall
[EMAIL PROTECTED]
change that first ? to be a * and
> > add (?:,\s*)* to the end
> >
> > while($challenge =~ s/^(?:\s*,)*\s*(\w+)=("([^\\"]+|\\.)*"|[^,]+)
> > \s*(?:,\s*)*//) {
> >
> > Graham.
>
> Yes, that seems to work too.
Committed to SVN
Thanks
Peter
--
Peter Marschall
[EMAIL PROTECTED]
you upgrade to perl-ldap 0.34 you may use Net::LDAP's host()
method that even works if you pass an array reference as first
parameter to Net::LDAP's constructor.
In perl-ldap 0.32 you may use the "net_ldap_host" key in the
Net::LDAP object: $ldap->{net_ldap_host} .
Hope th
s not write a "-\n" if there is
> only one attribute value change. I think perhaps it should.
It does if version => 1 is set (line 551 in current CVS).
Regards
Peter
--
Peter Marschall
[EMAIL PROTECTED]
x27;s success report I committed
Graham's patch SVN.
Out of curiosity:
Sven, Josef,
do you - by chance - have figures how it impacts performance?
To the bettor or towards the worse?
Peter
--
Peter Marschall
[EMAIL PROTECTED]
Hi,
On Tuesday, 22. May 2007 13:42, Graham Barr wrote:
> On May 20, 2007, at 7:46 AM, Peter Marschall wrote:
> > I have tried to write a little patch to Net::LDAP that should
> > implement support for IPv6.
> >
> > It tries to stay compatible as much as possible.
&g
set), but fails
with IPv6 in my ienvironment: the connection gets immediately
closed by the server.
This might be a problem of my environment or of the patch.
Currently I cannot tell, since this was my first tyoing with IPv6.
The more adventuresomes can try the attached patch.
Have fun, and please repo
order to build a list that
eventually becomes a hash in the called functions.
When the attribute does not exist, an empty list is returned,
making the hash-detection get mis-aligned and thus crete
the error above.
A fix has just been committed to SVN.
Regards
Peter
--
Peter Marschall
[EMAIL PROTECTED]
uld support IPv6,
but corrently don't?
Thanks for clarification
PEter
--
Peter Marschall
[EMAIL PROTECTED]
t hould work.
> I did experiment with references, but that only gives me errors
> that say the reference isn't blessed. If I bless it I get an error
> saying that it's not a reference.
No need to work with references of objects.
A Perl object is simply a bledded reference.
Peter
--
Peter Marschall
[EMAIL PROTECTED]
the standard.
Regards
Peter
--
Peter Marschall
[EMAIL PROTECTED]
1 - 100 of 284 matches
Mail list logo
