[
Date Prev
][
Date Next
]
[Chronological]
[Thread]
[Top]
Failed bind registry
To
:
openldap-technical@openldap.org
Subject
:
Failed bind registry
From
:
David Tello <
david.tello.wbsgo@gmail.com
>
Date: Wed, 15 Jan 2014 11:08:04 +0100
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=/gZ4DfIgLcVFK4tVq6CU64PVKABMF5PBYh8bV9pcD+U=; b=ahnyjKQEjZok+RlGEOj1iAT4+9/q8QieBqyZTozYk360hKwoYKf+fTmEG+kVqbM2Vx 5K3bY9z/Ea3VXWCcVyBGsdu9OhlUOO6fTQheEjjYuhacCHstmfqLiGE3l56D5bHLxA7a CjW7g9e8lQxkXpTkww6Q3/z31ttnXO4XmiGlMXOww7iBmY9I0KNhARbWjoZL2fPjkSF9 ADNQyHrOhsTpRznbAiRRLabv1cMVrK+epdkgODBjHTumUVFwQJsWw4Wr8F/ev3whg1EQ dx1NefUuYFqtmy3kPCYxFb8azp/tU9ptKVSN79ndRllqoQcuwA8WMvJRPW4QxTUCpf8h YwWQ==
I need to have in a exploitable format the failed binds. Something similar to the correct binds in the accesslog. I have seen that some people talks about the use of loglevel 256, but i thing that is too hard. Any help would be welcome.
Thanks!
Follow-Ups
:
Re: Failed bind registry
From:
Clément OUDOT <clem.oudot@gmail.com>
Re: Failed bind registry
From:
Dieter KlÃnter <dieter@dkluenter.de>
Prev by Date:
Re: Antw: SSHA hashed passwords && retrieving the salt
Next by Date:
strange error with openldap 2.4 and sql backend
Index(es):
Chronological
Thread