summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* remove use of client_info lsa_info_pol.Luke Leighton1999-11-271-13/+17
|
* enhanced samuser command to do same thing as enumusers command (-g -u -a)Luke Leighton1999-11-274-43/+182
| | | | except with only one user. done by sharing same code.
* bug-fixing registry commands and the rpcclient "rpcclient" command.Luke Leighton1999-11-273-65/+122
| | | | | | | | | | | | the rpcclient "rpcclient" command allows user options to be reset (e.g the username / password) _without_ terminating rpcclient. try this: rpcclient -S srv1 -U% -l log srv1$ rpcclient -S srv2 srv2$ :-)
* whoa. _major_ restructure of rpcclient. fixed some buuugs, created a few.Luke Leighton1999-11-2615-838/+875
| | | | | | found out that getopt() _must_ have optind set to 0 before reuse. still haven't decided what to do with the net* api yet...
* this file manages client states associated with handles.Luke Leighton1999-11-261-0/+154
|
* previous commit added an abstraction function that didn't even haveLuke Leighton1999-11-254-77/+25
| | | | | struct cli_state, uint16 fnum into the code: rpc_hnd_api_req(). modified cli_lsarpc.c to use this. the rest is const issues.
* cool! completed a samr* API that _would_ look like an msdn samr* api...Luke Leighton1999-11-2510-796/+509
| | | | | | if microsoft bothered to publish it. actually, there are good reasons for not publishing it: people might write programs for it, and then those programs wouldn't work on nt5, for example...
* registry API moved over to new format. reg_connect() is the top-levelLuke Leighton1999-11-245-199/+324
| | | | | | function, which takes \\server_name. tested a _few_ functions. found that regcreatekey receives a Fault PDU.
* service control manager API completed. svcenum -i works, but does notLuke Leighton1999-11-247-132/+141
| | | | do so twice. possible memory corruption, revolving around getopt().
* ok. *whew*. this is the first completed part of the restructure.Luke Leighton1999-11-2415-153/+153
| | | | | | | | | | | | verified that lsaquery, lsalookupsids work, and found some bugs in the parameters of these commands :-) soo... we now have an lsa_* api that has the same arguments as the nt Lsa* api! cool! the only significant coding difference is the introduction of a user_credentials structure, containing user, domain, pass and ntlmssp flags.
* first stages of removing struct cli_state* and uint16 fnum from allLuke Leighton1999-11-2414-214/+230
| | | | | | | | | msrpc client code. the intent is to hide / abstract / associate connection info behind policy handles. this makes the msrpc functions look more and more like their nt equivalents. who-hou!
* WARNING! MOVED rpc_server/srv_lsa_hnd.c TO lib/util_hnd.cLuke Leighton1999-11-245-28/+29
| | | | | | CVS UPDATE MAY ISSUE WARNING ABOUT lib/util_hnd.c MODIFICATION DATE BEING IN THE FUTURE. CVS CHECKOUT A NEW REPOSITORY MAY BE SAFER.
* rewrote policy handle code to be generic (it's needed for client-side too)Luke Leighton1999-11-2415-189/+469
| | | | attempted to fix regsetsec command
* oops, freed argc,argv arguments twice.Luke Leighton1999-11-231-2/+0
|
* attempted a svcset command. password is encrypted / messed up, thereforeLuke Leighton1999-11-237-254/+243
| | | | command fails.
* oops!!!! wrong command!!!Luke Leighton1999-11-234-4/+156
|
* adding svcctl 0x1b functionLuke Leighton1999-11-236-6/+339
|
* shuffling msrpc code around so that it can be used independently of rpcclientLuke Leighton1999-11-234-43/+91
|
* the last one. that concludes the removal of all next_token() callsLuke Leighton1999-11-222-60/+91
| | | | from rpcclient/cmd_*.c.
* another four next_token() removals (using getopt instead)Luke Leighton1999-11-224-32/+48
|
* another two.Luke Leighton1999-11-222-33/+39
|
* another oneLuke Leighton1999-11-221-18/+12
|
* moved two more commands over to getopt.Luke Leighton1999-11-222-22/+32
|
* okay :) all cmd_() functions now take int argc, char **argv :) thatLuke Leighton1999-11-2213-328/+368
| | | | | | | | | | | | means that some commands need more work, as they still use next_token(), the use of which i wish to avoid. plus, i was getting fed up of the poor command-line processing in some of these commands. i'm starting to need getopt() in them, especially in samsetuser. WARNING: only cmd_samr has been modded to use getopt() so far! reg commands won't work, esp.
* implement server-side generation of NTLMv2 session key. YESSS :-)Luke Leighton1999-11-216-30/+69
|
* you know what? this sort of thing makes me laugh. hmm, what functionsLuke Leighton1999-11-217-6/+48
| | | | | | | | | | | | | | | | | | | | have we got. and what data do we have. hmm.. i wonder what the NTLMv2 user session key can be... hmmm... weell.... there's some hidden data here, generated from the user password that doesn't go over-the-wire, so that's _got_ to be involved. and... that bit of data took a lot of computation to produce, so it's probably _also_ involved... and md4 no, md5? no, how about hmac_md5 yes let's try that one (the other's didn't work) oh goodie, it worked! i love it when this sort of thing happens. took all of fifteen minutes to guess it. tried concatenating client and server challenges. tried concatenating _random_ bits of client and server challenges. tried md5 of the above. tried hmac_md5 of the above. eventually, it boils down to this: kr = MD4(NT#,username,domainname) hmacntchal=hmac_md5(kr, nt server challenge) sess_key = hmac_md5(kr, hmacntchal);
* hmmm... have to add client-side support in domain_client_validate() toLuke Leighton1999-11-214-18/+42
| | | | _use_ user session key.
* adding user session key into network netlogon response.Luke Leighton1999-11-214-24/+53
|
* moving create user function into msrpc_samr.cLuke Leighton1999-11-212-51/+62
|
* oops, #ifdef'd cli_shutdown out, as the fun has _already_ started:Luke Leighton1999-11-201-2/+1
| | | | NT refuses to play nice, and establish a trust relationship.
* attempting to establish inter-domain trust relationships. modifiedLuke Leighton1999-11-202-28/+117
| | | | smbpasswd so it can be used to set up inter-domain trust account.
* modified domain_client_validate to take trust account name / type. thisLuke Leighton1999-11-207-15/+108
| | | | | | | | | | is to pass DOMAIN_NAME$ and SEC_CHAN_DOMAIN instead of WKSTA_NAME$ and SEC_CHAN_WKSTA. modified check_domain_security to determine if domain name is own domain, and to use wksta trust account if so, otherwise check "trusting domains" parameter and use inter-domain trust account if so, otherwise return False.
* doing a code reshuffle. want to add code to establish trust relationships.Luke Leighton1999-11-209-1746/+2078
|
* dynamic memory allocation i added a month ago: forgot to ZERO_STRUCT()Luke Leighton1999-11-202-0/+4
| | | | | | | | | some of the server-side stuff. Realloc() was being used, so it Realloc()d some random area of memory. oops.dynamic memory allocation i added a month ago: forgot to ZERO_STRUCT() some of the server-side stuff. Realloc() was being used, so it Realloc()d some random area of memory. oops.dynamic memory allocation i added a month ago: forgot to ZERO_STRUCT() some of the server-side stuff. Realloc() was being used, so it Realloc()d some random area of memory. oops.
* adding bits about SAM database security, and what the SAM commands areLuke Leighton1999-11-201-5/+30
| | | | actually for.
* explicit reference to tell people that rpcclient doesn't work withLuke Leighton1999-11-201-0/+5
| | | | | Windows 95. i can just imagine some people saying "it dunna wurk on my box at home", and me having to reply, "i dunna care".
* yodl updateLuke Leighton1999-11-204-32/+156
|
* oops.Luke Leighton1999-11-201-1/+1
|
* adding some command descriptions behind the rpcclient commands.Luke Leighton1999-11-201-14/+75
|
* yodl update - rpcclientLuke Leighton1999-11-199-16/+2065
|
* added an rpcclient man page. wow!Luke Leighton1999-11-193-5/+789
|
* nt5rc2 falling over because the LsaQueryInfoPolicy() response _must_Luke Leighton1999-11-193-2/+5
| | | | | | | | | | | have the string max length = string length + 1. if not, then it gets its knickers in a twist over whether the string is NULL-terminated or not. four days. four days i spent on this one.
* The First Necessary UNICODE String Support.Luke Leighton1999-11-193-32/+83
| | | | | | | | | the random workstation trust account password is TOTAL garbage. i mean, complete garbage. it's nowhere CLOSE to being a UNICODE string. therefore we can't just take every second character. created nt_owf_genW() which creates NT#(password) instead of NT#(Unicode(pw)). followed through to the password setting in srv_samr.c
* - surprise! the number of UNICODE strings that didn't have alignmentLuke Leighton1999-11-191-0/+20
| | | | after them is incredible. how did we get away with this for so long?
* - bug in nmbd registering DOMAIN_NAME<1c> to WINS server; recursionLuke Leighton1999-11-197-8/+124
| | | | | | | | desired flag MUST be set in any NBT UDP packets sent to a WINS server, else they will go to the WINS client side of the NT NetBIOS kernel instead, and will get trashed. - added \PIPE\browser server-side code.
* added \PIPE\browser plus experimental brsinfo command. you wouldn'tLuke Leighton1999-11-1910-2/+491
| | | | | believe the XXXX that MIGHT be involved in getting nt5rc2 to join a samba domain...
* responses to UDP samquery go back to SERVER<00> not DOMAIN<1c>, theLuke Leighton1999-11-184-14/+24
| | | | | | | request name. modified createuser rpcclient command to examine name being added. if it ends in a $, assume that a workstation trust account is being added.
* set "key does not exist" response to reg_query_val() (win32 status codeLuke Leighton1999-11-185-10/+70
| | | | of 0x2). [p.s. getting REALLY bored of this nt5rc2->samba domain stuff].
* added samuserset2 rpcclient command to test ACB_XXX bit-setting onLuke Leighton1999-11-187-11/+571
| | | | | samr opcode 0x25. _yet_ another failed attempt to get nt5rc2 to join a samba domain. what _is_ it with this stuff, dammit?
* updating reg_value_info() parsing code to take BUFFER2 instead of justLuke Leighton1999-11-186-46/+55
| | | | a char*. now copes with multiple types.