Age | Commit message (Collapse) | Author | Files | Lines |
|
in our new samr server
(This used to be commit 0f2503111498e809237e0155962db55dfde8cbfb)
|
|
added tests for the level 23 and 25 password change methods
(This used to be commit d49f7a6a0d1895de3d654a5b46c6aec3a57fde76)
|
|
thanks to Luke Howard for this test
(This used to be commit 891653e7d40f581016085e2c32e2802eea7e7ade)
|
|
afterwards for the RPC-NETLOGON test. This makes it much simpler to
run the test and also means that it doesn't distrurb any existing
domain join you might have.
(This used to be commit feac996794d5cc16e3612fb2901668a9b1e1d274)
|
|
(This used to be commit 4b4f025504cb5b92c8b119259f1df622cd72ec7c)
|
|
yay!
(This used to be commit 0221566cf5ff7dc5ce0de9af451b935ed8615f4e)
|
|
stick
(This used to be commit b2ebaf95b75b050ad02ca967867337cd81faa859)
|
|
(This used to be commit 0be7a866dc39e2d63c9c114d0f668287259e7c9e)
|
|
possibly destructive tests. Use with care!
Added IDL and test code for samr_Shutdown() and samr_SetDsrmPassword()
(This used to be commit 84de0b7e58c69e0817b9d475de0895a54cc95927)
|
|
request (a dead socket). I discovered this when testing against Sun's
PC-NetLink.
cleaned up the naming of some of the samr requests
add IDL and test code for samr_QueryGroupMember(),
samr_SetMemberAttributesOfGroup() and samr_Shutdown(). (actually, I
didn't leave the samr_Shutdown() test in, as its fatal to windows
servers due to doing exactly what it says it does).
(This used to be commit 925bc2622c105dee4ffff809c6c35cd209a839f8)
|
|
(for example, not filling in extra
fields in level21 setuserinfo)
(This used to be commit d06ed158f9aef94159bfc09065ca5ad0c4c99de3)
|
|
Also added much better handling of random password generation in the
password change test code
(This used to be commit 67ae0b2a9851c1e77fdaa9f317a83bd54950618f)
|
|
samr_GetBootKeyInformation() and samr_Connect3()
also added some stub IDL for samr_SetBootKeyInformation() although I
don't yet have working test code. This one is tricky, as if you get it
wrong then the target system won't boot any more :)
(This used to be commit 118b6fc292ba3257511b1b83846582013fb59b23)
|
|
- completed the IDL and test code for the various set user password
mechanisms in samr. Three password mechanisms are now working, the
UserInfo24 method, the OemChangePasswordUser2() method (which only
sets the LM password) and the ChangePasswordUser2() method which sets
both the LM and NT passwords.
- updated some crypto routines to support the password change tests
(This used to be commit 051efa2abf9d1fbbf783df411c02f2714027f813)
|
|
samr_AddMultipleMembersToAlias(),
samr_RemoveMultipleMembersFromAlias(), samr_OemChangePasswordUser2(),
and samr_ChangePasswordUser2()
The password change functions don't actually work yet (but should
soon). At this stage I have just completed the IDL for them. Next step
is to get the hash verifiers right and the torture test should be able
to do password changes.
(This used to be commit 849d0d314a2add80f2b2be6b503fea05973f998e)
|
|
samr_QueryUserInfo2(), samr_QueryDisplayInfo2() and
samr_GetDisplayEnumerationIndex2()
(This used to be commit fddda52500d482bde79994c14a0a822a1d305ac3)
|
|
samr_GetDisplayEnumerationIndex(), samr_TestPrivateFunctionsDomain(),
samr_TestPrivateFunctionsUser() and samr_RemoveMemberFromForeignDomain()
(This used to be commit 53c66708874f9f8e7868530cd2a780160e2eca01)
|
|
a few more samr functions). Still a hack tho.
(This used to be commit 15199a384f63ff206c8bcd483d615a3f91e9877d)
|
|
(This used to be commit 747351140b839879abe1a79a005d81ca4b35a658)
|
|
(This used to be commit 0b8203306d9eb61aaec9549d56c40831fcd091c3)
|
|
(This used to be commit fe1fc81ba76515b79069881d2d62f60201314d04)
|
|
test code
(This used to be commit 46185a71ba0e06544cacf117654e4dbf39385378)
|
|
(This used to be commit 9f12fb39dbac886582d0ccce418491522c042fe6)
|
|
group names.
Volker
(This used to be commit 481cec94c47ffda341e00d628cf34c2c7b5de2fa)
|
|
(This used to be commit 02ddf78e5563b15cb45ae4bc6234469be0dc0210)
|
|
(This used to be commit 0a67057e9626c1539f964e978537e24544784263)
|
|
- Small fixess in nt4 and dir backends
- Start on w95 file backend
(This used to be commit aa739e8d3c7108f6f2089af2d8d522feacc7f698)
|
|
(This used to be commit 1d8a6d762aa4dab54bb58959cb1e7957a76e5b6e)
|
|
(This used to be commit dcb172d207ca0b56e62165633b2f7f7fcc188f7c)
|
|
- Start with the LDB backend
- The API is now more windows-like, which should make it easier to use
in rpc_server
- Added a GTK+ front-end
- Added some more IDL
More updates will follow, especially in the RPC field..
(This used to be commit 3adffa021779b26047a20f16a3c0b53d74751560)
|
|
this required some crypto infrastructure and some sid utilities
(This used to be commit 37d0efa9c2af8532536bea88412f0dd3ed39ecfc)
|
|
(This used to be commit 1396db85372af1824592ef66f963603e3f35803c)
|
|
- Add some initial implementation of the ldb backend
- More checks in the winreg torture test
(This used to be commit ae2b63b6f1821bc4f693cb8e2a5f78718c483c24)
|
|
(This used to be commit 9f13b7c60cc7e6edd095eee96625ee02cd0dd73b)
|
|
(This used to be commit 8b9b992f6026a6b9ace7564d6aaac9060a54af7d)
|
|
(This used to be commit dd95cd141dc63f16e14f4c9392529653084b5a2a)
|
|
(This used to be commit 4de08b64ddb3851e90a8dadd7d0d0991e933abf5)
|
|
(This used to be commit cdb47511531cb8ef19334088eecb14971e189a4f)
|
|
also tested lsa_Delete() to delete the newly created account
(This used to be commit c4d5d0e9eba6b564e2ce6885d66d644b6612d721)
|
|
(This used to be commit ccce61287de07684159e2de990773f4098e07652)
|
|
(This used to be commit e0eb4b3cfb75385ff7a012ca0f8fad1278c195d9)
|
|
e.g.
ncacn_np:myserver:[samr,sign,print]
will now enable the packet debugging
and the debugging is not bound anymore to the debuglevel >= 2
in the torture tests
- also the dcesrv_remote module now supports debugging of the packets
use the 'dcerpc_remote:binding' smb.conf parameter.
metze
(This used to be commit 40abf3c584efed7f977ddd688ea064540e5a5b13)
|
|
incorrect policy handle
(This used to be commit 8cd6e90eb8716ba43f5940245d7be580aab4ba83)
|
|
handles are not shared between open dcerpc connections, even when
those connections are on the same SMB socket. I have tested this with
w2k3, w2k and NT4. It seems that policy handles have a strict scope of
the dcerpc connection on which they were opened.
I realise that this goes against existing folk-law in the team, but it
seems that the previous testing (I'm not sure who did this?) was
wrong. Perhaps clients do send us policy handles from other
connections, but if they do then the correct thing to do is to fail
the operation with a dcerpc fault. I suspect that failing it with
exactly the right dcerpc fault code is important.
(This used to be commit 2ed24d29bafd9055d5782acdd595cd0f378a651a)
|
|
(This used to be commit 2372321eedb6d446c1555ed318bd98743cabaaa0)
|
|
(This used to be commit 6319166420ba7cd7bb3a69d88510d8e6216c7c89)
|
|
(This used to be commit 564e505e925d67be00ca2cbe21b2b9b33a1ac0c7)
|
|
(This used to be commit 9d3e06f0e312c5585701aa385132f23dfb2917eb)
|
|
we needed to adjust the alignment of [relative] buffers for this to
work. I wonder if they are always 4 byte aligned?
(This used to be commit 9cd0a0b8b976e62c6da71b7e55cba5b38483620d)
|
|
(This used to be commit abe7ffcece5fcb75b0cf5633dd5871fa3e3c1723)
|