| commit | 2544ba6a0a1b9c4bacc93262b8e776bf98456252 | |
| author | Volker Lendecke <vl@samba.org> | |
| Thu, 5 Mar 2009 21:20:55 +0000 (5 22:20 +0100) | ||
| committer | Volker Lendecke <vl@samba.org> | |
| Thu, 5 Mar 2009 21:28:07 +0000 (5 22:28 +0100) | ||
| tree | 279b0427024c622595e3f06b3470676c227e403f | treesnapshot (tar.gz zip) |
| parent | bb1dab3a97d07dd6778f414ce3bff4f150b60d5d | 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
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
| source3/rpc_server/srv_pipe.c | diffblobblamehistory |