[Samba] eventlog functionality

Andrew Bartlett abartlet at samba.org
Tue Sep 11 15:21:31 UTC 2018

On Tue, 2018-09-11 at 15:14 +0000, ray klassen via samba wrote:
> Yes, after further research the solution could possibly be to create
> a python script to monitor the json output in log.samba and push out
> eventlog formatted events to 'Security' with eventlogadm. Seems a lot
> of work.

That still assumes the appliance is reading the same type of event log
(because the eventlog RPC service was superseeded by eventlog6 and the
WMI thin, which is the reason I asked for details). 

> The appliance in question also supports getting the necessary info
> via the netapi call "netsessionenum" I have tried that and a
> wireshark dump shows samba replying with WERR_INVALID_LEVEL. 

> if you could shed any light on that, I would appreciate it.

If you could get the exact details on that, or the capture file if not
confidential, that would be good.

Note however that the Samba AD DC doesn't have a persistent connection
from the client unless you mount a share, so even if it worked it
wouldn't show up all the clients reliably. 

(A domain login to AD can be done with just a kerberos ticket

Andrew Bartlett

>     On Monday, 10 September 2018, 18:03:12 GMT-7, Andrew Bartlett via
> samba <samba at lists.samba.org> wrote:  
>  On Mon, 2018-09-10 at 21:26 +0000, ray klassen via samba wrote:
> > 
> > we have recently purchased a security appliance that wants to poll
> > the DC's for login info (ipaddress:logged-in-user) to give more
> > granular access to internet resources
> > this seems possible with samba 4.8.4
> > 
> > my smb.conf
> > 
> >     log level = 1 auth_audit:3
> >     eventlog list = Application System Security SyslogLinux
> > 
> > 
> > It doesn't look like audit events are ending up in
> > /usr/local/samba/var/locks/eventlog/security.tdb
> > which where they might go.
> > I certainly am seeing lots of login audit info in log.samba, so
> > that's working. 
> Currently this isn't connected up.  And even if it were, a recent
> study
> of similar appliances showed that they were not using the old NT4
> eventlog, but WMI over DCOM to access the logs, both of which we
> don't
> support.
> https://wiki.samba.org/index.php/Event_Logging#Future_Support_for_thi
> rd_party_clients
> If you can work out which protocol your particular appliance is
> connecting to AD with (you might need to try against windows and
> watch
> with wireshark), we can at least tell you on a scale of 'hard, very
> hard, extremely hard' it would be to add.
> Sorry,
> Andrew Bartlett
> -- 
> Andrew Bartlett                      http://samba.org/~abartlet/
> Authentication Developer, Samba Team  http://samba.org
> Samba Developer, Catalyst IT          http://catalyst.net.nz/services
> /samba
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
Andrew Bartlett                       http://samba.org/~abartlet/
Authentication Developer, Samba Team  http://samba.org
Samba Developer, Catalyst IT          http://catalyst.net.nz/services/samba

More information about the samba mailing list