The branch, v3-2-test has been updated via 91e2cd86e24cead352f07cc1a6b4a8e3a364adb5 (commit) from 43ea27319933f3b49b61decde8321d9162cfd9ef (commit)
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=v3-2-test - Log ----------------------------------------------------------------- commit 91e2cd86e24cead352f07cc1a6b4a8e3a364adb5 Author: Volker Lendecke <v...@samba.org> Date: Thu Mar 5 15:12:55 2009 -0800 Complete the fix for bug 6100 According to [MS-RPCE].pdf, section 2.2.2.11: ---- A client or a server that (during composing of a PDU) has allocated more space for the authentication token than the security provider fills in SHOULD fill in the rest of the allocated space with zero octets. These zero octets are still considered to belong to the authentication token part of the PDU.<36> ---- RPC implementations are allowed to send padding bytes at the end of an auth footer. Windows 7 makes use of this. Thanks to Nick Meier <nme...@microsoft.com> Volker ----------------------------------------------------------------------- Summary of changes: source/rpc_server/srv_pipe.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) Changeset truncated at 500 lines: diff --git a/source/rpc_server/srv_pipe.c b/source/rpc_server/srv_pipe.c index 05cdb65..65bc0ae 100644 --- a/source/rpc_server/srv_pipe.c +++ b/source/rpc_server/srv_pipe.c @@ -2101,7 +2101,7 @@ bool api_pipe_schannel_process(pipes_struct *p, prs_struct *rpc_in, uint32 *p_ss auth_len = p->hdr.auth_len; - if (auth_len != RPC_AUTH_SCHANNEL_SIGN_OR_SEAL_CHK_LEN) { + if (auth_len < RPC_AUTH_SCHANNEL_SIGN_OR_SEAL_CHK_LEN) { DEBUG(0,("Incorrect auth_len %u.\n", (unsigned int)auth_len )); return False; } -- Samba Shared Repository