summaryrefslogtreecommitdiff
path: root/source3/rpcclient
diff options
context:
space:
mode:
authorAndrew Bartlett <abartlet@samba.org>2001-07-10 17:02:02 +0000
committerAndrew Bartlett <abartlet@samba.org>2001-07-10 17:02:02 +0000
commite4b6f641e8590b385672e12f4a2829c69e2d33aa (patch)
tree076872ef154e69c2aa61685d4a6a9dbd0c623822 /source3/rpcclient
parent973a78c2db1e15fc0a88b15d8857a8d7cf46a140 (diff)
downloadsamba-e4b6f641e8590b385672e12f4a2829c69e2d33aa.tar.gz
samba-e4b6f641e8590b385672e12f4a2829c69e2d33aa.tar.bz2
samba-e4b6f641e8590b385672e12f4a2829c69e2d33aa.zip
This fixes security=domain, which has been broke since the big charset
changeover. For my own sainity I have created a new function to fill out both the header and buffer for a string in an RPC struct. This DOES NOT take a length argument, only the actual string to be placed. The RPC code is currently littered with code that does init_uni_hdr() followed immidiatly by init_unistr2(), and often the length argument is wrong. (It was for the code I changed, even before the charset stuff). Another bug where we made strings AT LEAST MAX_UNICODE_LEN long hid this bug. This works for loopback connections to Samba, and can't be any more broke than it was before :-). (We had double and revese conversions, fun...). In particular this makes us multibyte complient. In any case, if there are no objections I will slowly convert other bits of code to the same system. (This used to be commit cf1d1cd9d6362f6e32ed9c2f6d2f6f25c47705ad)
Diffstat (limited to 'source3/rpcclient')
0 files changed, 0 insertions, 0 deletions