librpc/idl: Explain why PAC_TYPE_CLIENT_CLAIMS_INFO is not directly decoded

Signed-off-by: Andrew Bartlett <abartlet@samba.org>
Reviewed-by: Douglas Bagnall <douglas.bagnall@catalyst.net.nz>

diff --git a/librpc/idl/krb5pac.idl b/librpc/idl/krb5pac.idl
index 6655e2ff5b772f7e5a279fd42719ff02c2aa51b7..77189bb929bdaa0c1a0c770d8725cf5dd8860f26 100644 (file)
--- a/librpc/idl/krb5pac.idl
+++ b/librpc/idl/krb5pac.idl
@@ -194,6 +194,14 @@ interface krb5pac
                [case(PAC_TYPE_TICKET_CHECKSUM)]        PAC_SIGNATURE_DATA ticket_checksum;
                [case(PAC_TYPE_ATTRIBUTES_INFO)]        PAC_ATTRIBUTES_INFO attributes_info;
                [case(PAC_TYPE_REQUESTER_SID)]  PAC_REQUESTER_SID requester_sid;
+               /*
+                * [subcontext(0)] and DATA_BLOB_REM is used as in
+                * PAC_TYPE_CLIENT_CLAIMS_INFO
+                * PAC_TYPE_DEVICE_CLAIMS_INFO as Windows will
+                * sometimes send an empty buffer (presumably to avoid
+                * the overhead of the header around the claims) if
+                * there are no claims to send
+                */
                [case(PAC_TYPE_CLIENT_CLAIMS_INFO)][subcontext(0)] DATA_BLOB_REM client_claims_info;
                [case(PAC_TYPE_DEVICE_INFO)][subcontext(0xFFFFFC01)] PAC_DEVICE_INFO_CTR device_info;
                [case(PAC_TYPE_DEVICE_CLAIMS_INFO)][subcontext(0)] DATA_BLOB_REM device_claims_info;