search for: nt_user_token

hello everyone, i'm not even sure there is something wrong with samba here but im taking all chances... i have a linux samba server and 3 winXP prof pcs in my setup. now from one of the winxp boxes i can not seem to access my shares on the server. that is when i try to go through network neighborhood path. the message that is returned is : \\stargaze is not accessible. You may not have

...and I supress my account from group. since more than 1 hour, I can see and acces to directory but in unix console I cannot and I must don't access to this directory. The only possibility than I have is : "killing my connection with SWAT" I looking the source and I think that is the NT_USER_TOKEN information is not updated after connection or if these informations is updated not correctly. I propose that samba refresh correcly these information every five minutes or a parameter REFRECH_USRE_INFO in smb.conf. please help me. St?phane Samba Administrator. ------------------------...

Is behavior of ACLs under Samba 3.3.0 (Sernet) completely different from that under version 3.2.7? The release notes only talks about some "fixes". I installed version 3.3.0 and got completely different result with the same filesystem and the exact same samba configuration. The ACLs behaved strangely and appeared very different under Windows ACL editor. Users were now unable to

...internal error unable to produce a stack trace on this platform unable to change to /var/log/samba/cores/smbd refusing to dump core talloc report on 'null_context' (total 4485 bytes in 176 blocks) REGISTRY_KEY contains 128 bytes in 9 blocks (ref 0) 0x3ab110 NT_USER_TOKEN contains 364 bytes in 2 blocks (ref 0) 0x3aac80 SORTED_TREE contains 527 bytes in 44 blocks (ref 0) 0x3aa220 main loop talloc (mainly parse_misc) contains 1369 bytes in 19 blocks (ref 0) 0x3a9d80 struct pdb_methods contains 1...

...} set_sec_ctx(uid, gid, current_user.ngroups, current_user.groups,token); /* * Free the new token (as set_sec_ctx copies it). */ if (must_free_token) delete_nt_token(&token); ^^^^^^^^^^^^^^^^^^^^^^^^- here current_user.nt_user_token becomes invalid. You can triger the bug, if you connect to a printer share with a 'force group = agroup' option an try to print. SIGSEGV. I think the following patch should fix the problem. --- samba-2.2.1a/source/smbd/sec_ctx.c~ Fri Jul 6 04:02:03 2001 +++ samba-2.2.1a/source/smbd/sec...

...<http://lists.samba.org/mailman/listinfo/samba>, <mailto:samba-request@lists.samba.org?subject=unsubscribe> List-Archive: http://lists.samba.org/pipermail/samba/ Anselm Kruis wrote: > > Hi, > > there is a bug in set_sec_ctx(). At the end of the function > current_user.nt_user_token is set to token instead to the copy of token. > But the function become_user() assumes, that set_sec_ctx uses a copy of > token. That leads to an invalid content of the global variable > current_user.nt_user_token Spot on ! Excellent work thanks ! I've applied this fix to HEAD and 2....

...112, st_atime = 994072899, __unused1 = 0, st_mtime = 993039758, __unused2 = 0, st_ctime = 994072898, __unused3 = 0, __unused4 = 0, __unused5 = 0} bad_path = 0 access_mode = 0 action = 1 ecode = 0 user = {conn = 0x81ec938, vuid = 100, uid = 507, gid = 507, ngroups = 1, groups = 0x81eb4e8, nt_user_token = 0x81eb4f8} user_name = "eelco", '\000' <repeats 11 times>, "'\000\000\000uF\b@", '\000' <repeats 16 times>, ",m?tw?\000\000\000\000\001\000\000\000\000\000\000\0001\000\000\000\000\000\000\000O\016\023\b\000\000\000\000uF\b@`{\b@\000\000\0...