| commit | b7e092783f4a3ea7ef1c62400b7e445eb1e879e1 | |
| author | Volker Lendecke <vl@samba.org> | |
| Thu, 5 Mar 2009 23:12:55 +0000 (5 15:12 -0800) | ||
| committer | Karolin Seeger <kseeger@samba.org> | |
| Fri, 27 Mar 2009 12:06:51 +0000 (27 13:06 +0100) | ||
| tree | dee492ce6d0ae931bc5453661da347e521decc24 | treesnapshot (tar.gz zip) |
| parent | 388c52ee16e42b8c637adee8e6e181117bcded5f | commitdiff |
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 <nmeier@microsoft.com>
Volker
(cherry picked from commit 91e2cd86e24cead352f07cc1a6b4a8e3a364adb5)
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 <nmeier@microsoft.com>
Volker
(cherry picked from commit 91e2cd86e24cead352f07cc1a6b4a8e3a364adb5)
| source/rpc_server/srv_pipe.c | diffblobblamehistory |