summaryrefslogtreecommitdiffstats
path: root/source3
Commit message (Collapse)AuthorAgeFilesLines
...
* s3:torture:delete: simplify return code handling, fixing a couple of return ↵Michael Adam2012-08-091-48/+3
| | | | codes in error cases
* s3:torture:delete: reduce indentationMichael Adam2012-08-091-8/+6
|
* s3:torture:delete: add a commentMichael Adam2012-08-091-0/+2
|
* s3:torture:delete: add a commentMichael Adam2012-08-091-0/+2
|
* s3:torture:delete: add a commentMichael Adam2012-08-091-0/+2
|
* s3:torture:delete: move the success message for a subtest to the correct placeMichael Adam2012-08-091-2/+3
|
* s3:torture:delete: remove an else, reducing indentationMichael Adam2012-08-091-2/+3
|
* s3:torture:delete: remove an else, reducing indentationMichael Adam2012-08-091-2/+3
|
* s3:torture:delete: remove an else, reducing indentationMichael Adam2012-08-091-2/+3
|
* s3:torture:delete: remove an else, reducing indentationMichael Adam2012-08-091-2/+3
|
* s3:torture:delete: really fail the test in a failure caseMichael Adam2012-08-091-2/+2
|
* s3:torture:delete: fix a commentMichael Adam2012-08-091-1/+1
|
* s3:torture:delete: fix a messageMichael Adam2012-08-091-1/+1
|
* s3:torture:delete: fix a messageMichael Adam2012-08-091-1/+1
|
* s3:torture:delete: fix a messageMichael Adam2012-08-091-1/+1
|
* s3:torture:delete: fix a message (counting the opens)Michael Adam2012-08-091-1/+1
|
* s3:torture:delete: untangle function call from result checkMichael Adam2012-08-091-1/+2
|
* s3:torture:delete: untangle function call from result checkMichael Adam2012-08-091-1/+2
|
* s3:torture:delete: untangle function call from result checkMichael Adam2012-08-091-2/+6
|
* s3:torture:delete: untanlge function call from result checkMichael Adam2012-08-091-1/+2
|
* s3:torture:delete: untangle function call from result checkMichael Adam2012-08-091-1/+2
|
* s3:torture:delete: untangle function call from result checkMichael Adam2012-08-091-1/+2
|
* s3:torture:delete: untangle function call from result checkMichael Adam2012-08-091-1/+1
|
* s3:torture:delete: untangle function call from result checkMichael Adam2012-08-091-1/+2
|
* s3:torture:delete: untangle function call from result checkMichael Adam2012-08-091-1/+2
|
* s3:torture:delete: untangle function call from result checkMichael Adam2012-08-091-1/+2
|
* s3:torture:delete: untangle function call from result checkMichael Adam2012-08-091-3/+5
|
* s3:torture:delete: untangle function call from result checkMichael Adam2012-08-091-1/+2
|
* s3:torture:delete: untangle function call from result checkMichael Adam2012-08-091-2/+5
|
* s3-events: Do not vasprintf() the tevent debug messages that will not be shownAndrew Bartlett2012-08-091-4/+6
| | | | | | | This malloc() and free() actually shows up quite high on a call profile of provision of the AD DC (and this is the matching patch for source3). Andrew Bartlett
* s3:smb2_sesssetup: setup global->[en|de]cryption_keyStefan Metzmacher2012-08-091-0/+36
| | | | | | | metze Autobuild-User(master): Stefan Metzmacher <metze@samba.org> Autobuild-Date(master): Thu Aug 9 09:59:02 CEST 2012 on sn-devel-104
* s3:smb2_read: don't try sendfile if encryption is usedStefan Metzmacher2012-08-091-0/+1
| | | | metze
* s3:smb2_server: add smbd_smb2_request->do_encryptionStefan Metzmacher2012-08-092-0/+2
| | | | | | For now it's always false... metze
* s3:smb2_tcon: set global->encryption_required and enforce itStefan Metzmacher2012-08-091-5/+29
| | | | | | | This the account or client doesn't support encryption we should reject the tree connect. metze
* s3:smb2_sesssetup: set global->encryption_required and enforce itStefan Metzmacher2012-08-091-0/+22
| | | | | | | This the account or client doesn't support encryption we should reject the session setup. metze
* s3:smbXsrv.idl: add encryption_required to smbXsrv_tcon_global0Stefan Metzmacher2012-08-091-0/+1
| | | | metze
* s3:smb2_server: check the session before we could response with an error.Stefan Metzmacher2012-08-091-15/+15
| | | | metze
* s3:smb2_server: do central file_id check if the operation requires itStefan Metzmacher2012-08-091-0/+56
| | | | | | | Note that it's fine to call file_fsp_smb2() twice, the 2nd call just returns smb2req->compat_chain_fsp without a 2nd lookup. metze
* s3:nmbd: log a failure in get_domain_master_name_node_status_success() as ↵Stefan Metzmacher2012-08-081-1/+1
| | | | | | | | | level 1 metze Autobuild-User(master): Stefan Metzmacher <metze@samba.org> Autobuild-Date(master): Wed Aug 8 20:14:29 CEST 2012 on sn-devel-104
* s3:nmbd: don't log get_domain_master_name_node_status_fail at level 0Stefan Metzmacher2012-08-081-1/+1
| | | | metze
* s3:smb2_server: s/i/idx in smbd_smb2_request_pending_queue()Stefan Metzmacher2012-08-081-4/+4
| | | | | | | metze Autobuild-User(master): Stefan Metzmacher <metze@samba.org> Autobuild-Date(master): Wed Aug 8 17:32:26 CEST 2012 on sn-devel-104
* s3:smb2_server: make use of SMBD_SMB2_OUT_HDR_PTR() in ↵Stefan Metzmacher2012-08-081-1/+1
| | | | | | smbd_smb2_request_pending_queue() metze
* s3:smb2_server: remove useless variable 'i'Stefan Metzmacher2012-08-081-2/+1
| | | | metze
* s3:smb2_server: rewrite dup_smb2_vec3() using SMBD_SMB2_*_IOV_OFS and helper ↵Stefan Metzmacher2012-08-081-42/+52
| | | | | | variables metze
* s3:smb2_server: make use of SMBD_SMB2_* macros in smbd_smb2_request_done_ex()Stefan Metzmacher2012-08-081-18/+21
| | | | metze
* s3:smb2_server: make use of SMBD_SMB2_* macros in ↵Stefan Metzmacher2012-08-081-8/+14
| | | | | | smbd_smb2_request_verify_sizes() metze
* s3:smb2_server: use the common buffer layout for smbd_smb2_request_pending*Stefan Metzmacher2012-08-081-16/+26
| | | | metze
* s3:smb2_read: use SMBD_SMB2_NUM_IOV_PER_REQ when checking for sendfile() supportStefan Metzmacher2012-08-081-1/+1
| | | | metze
* s3:smb2_read: fix indentation in schedule_smb2_sendfile_read()Stefan Metzmacher2012-08-081-8/+8
| | | | metze
* s3:smb2_server: don't try to update req->in.vector[0] in ↵Stefan Metzmacher2012-08-081-3/+0
| | | | | | | | | | smbd_smb2_request_pending_queue() req->in.vector[0] is reserved for the transport and might be removed in future. This is currently always { NULL, 0 }, as it's not used, by our transport layer code. The SMB2 layer should never touch this! metze