dstrace is probably your best bet. You already know the alternatives
better than most (future). You can use Audit to log all authentications
and then use Audit notifications to possibly limit some by client (being
the server) but it's not perfect.
Good luck.
Jeff Johnson wrote:
> anyone know when there will a way to log ldap binds??
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGvMHQ7eGRNwWOK9IRAlkcAKCgOmWFXlhGcsLh6VLundjXKxmVbwCeJsgr
eUn4uMlSG2d3Q9On+PUigiU=
=gIul
-----END PGP SIGNATURE-----
nsure audit doesnt log ldap binds,,,just ncp afaik.
True.
Good luck.
Jeff Johnson wrote:
> dstrace wont help me. i need something to run continuously,,like an nsure
> audit agent.
>
> nsure audit doesnt log ldap binds,,,just ncp afaik.
>
> On Fri, 10 Aug 2007 19:51:36 +0000, a...@novell.com wrote:
>
> dstrace is probably your best bet. You already know the alternatives
> better than most (future). You can use Audit to log all authentications
> and then use Audit notifications to possibly limit some by client (being
> the server) but it's not perfect.
>
> Good luck.
>
>
>
>
>
> Jeff Johnson wrote:
>>>> anyone know when there will a way to log ldap binds??
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGvMNU7eGRNwWOK9IRAuDtAKCuPaM0BsWvDgpQJqfspjYxYt2MpgCfVlWC
QYaR6VFjax+2Pi8OkwxryGo=
=icuZ
-----END PGP SIGNATURE-----
> dstrace wont help me. i need something to run continuously,,like an
> nsure audit agent.
>
> nsure audit doesnt log ldap binds,,,just ncp afaik.
>
Sentinel ?
--
Cheers,
Edward
Sentinel uses the Audit Platform Agents and Instrumentation to collect data.
Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGv9SN7eGRNwWOK9IRAuHnAKCBbpgFOLODFqqNNGaYBP5jE05B5ACeNSFf
CT8oKUCzJ4rNFf2HOFXt4gY=
=kTH/
-----END PGP SIGNATURE-----
Don
--
D.Lohr
Technical Services
James Madison University
++ Bad command or file name ++
In Audit a field contains the IP address where the event originated
which, in the case of a login, should be the client. In the case of
LDAP the "client" is the LDAP client on the server which is the client
of eDirectory instead of the LDAP client on the user side. Doesn't help
as much as it could.
Good luck.
iD8DBQFGwG1Y7eGRNwWOK9IRAi8jAJsG7Cs/lXSn+7B0yU/WJ6MaiA26iQCbBcRl
dyRmCFdym/Lg6GOgiJtM2iU=
=1T5X
-----END PGP SIGNATURE-----
Even when doing dstrace and packet scanning with the pktscan.nlm, the
user's workstation is not in the packet when the user is authenticating
into an application configured to use an ldap server. It shows that
applications server's address as the ldap client.
My reason for asking Jeff, (what was he hoping for), was to make sure HE
understood that the user's workstation address is not even available in
dstrace and pktscan files on his applications/services that are
configured to use his ldap service.
Don
--
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Sentinel uses the Audit Platform Agents and Instrumentation to
> collect data.
Correct and that will give him the information of LDAP I presume or
isn't LDAP stuff being logged ?
--
Cheers,
Edward
If Audit could do it he probably wouldn't be asking (Jeff knows Audit
better than me). I guess more to the point the Audit stuff gets the
information in its limited-usability form which means that Sentinel will
as well. I think I'm misunderstanding you but the long and short is
that Audit can't get the info and therefore neither can Sentinel (in
this case... Sentinel is obviously much more powerful than Audit but
we're limited by the Audit components which both products use).
Good luck.
Edward van der Maas wrote:
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGwOTd7eGRNwWOK9IRAue9AJ9hEVcTBqT18hbysALjk7zsaD5hIACfZGUD
WfjOopZ+qyZrqDqDeugoQIo=
=P1JB
-----END PGP SIGNATURE-----