Somebody help me to find where is source code(file) to capture following information in samba4

[KS Tan]

Hi Andrew,
Actually I want to know more about the KDC ticket issue/release, and
after want to know the 
1. username, computername, ipaddress.
2. After user logout, the session expired (ticket expired).

About the script, I just wanted to use customized OU and add a field
inside to put the script path (The script is not assign to the user). 

Below is what I'd test/result inside latest source code: 
1. seems latest source is near to the OU+GPO. So far I able to manually
Link Default Domain GPO into particular OU via SWAT(using field gPLink),
and the GPO show inside my OU at the dsa.msc.

2. I try to create few new GPO inside the sysvol, and I'd link it to my
OU using swat. Inside dsa.msc show me permission denied.

3. I'd join Windows 2003 Enterprise into the samba4 active directory,
when I want to promote it to additional domain controller, it failed (I
guess this is nothing new).

4. So far I able to add/delete object from dsa.msc. It's great!


So, I'm waiting the further development until swat allow me to add new
GPO(Or at least, I can copy paste from defauly domain policy). Then I'll
come out another brand new real live CD, which will simulate a real
corporate environment to eveybody review(I hope that time the Dynamic
register dns services is ready too, so I can let user perform zone
transfer).

Ks


Rita, 

On Mon, 2007-08-06 at 16:21 +1000, Andrew Bartlett wrote:
> On Sat, 2007-08-04 at 13:25 +0800, KS Tan wrote:
> > Hi all,
> > 
> > Due to I don't have much knowledge in samba source code and I don't want
> > to mess up the development. So I want to do my own testing inside the
> > samba 4 source code. So, anybody can tell me which file I should edit to
> > achive following task:-
> > 
> > 1. After user logon, I want to know who is the user and I want to
> > perform some action inside the source code.
> 
> What type of logon are you looking for?  
> 
>  - CIFS connections (such as mounting a drive)?
>  - KDC ticket issue?
>  - NT4-style SamLogon over NETLOGON?
> 
> > 2. After user logout, I want to know who is the user  and I want to
> > perform some action inside the source code.
> 
> We can only detect logout for CIFS connections, when the user
> disconnects. 
> 
> > 3. After user logon, I want to choose a script and ask the user to run
> > the script.
> 
> Just set the scriptPath attribute on the user. 
> 
> > I don't mind to open up 10-20 pages of source code to achieve my goal,
> > but the problem is I totally don't know where to start.
> 
> All logins (and ticket issue) will at some point go via
> authsam_account_ok() in auth/sam.c, to check that the user is
> authorized.  
> 
> New CIFS sessions will be recorded in smbsrv_session_new() in
> smb_server/session.c
> 
> As I mention above, logoffs are tricky, but see
> smbsrv_session_destructor() in smb_server/session.c for CIFS sessions.  
> 
> I hope this helps.  I could add some hooks (particularly for scripts) to
> these events, to help admins instrument this code, if it would be
> useful.
> 
> Andrew Bartlett
>