cope with arbitrary unknown pac buffer types, so when MS adds

a new one we don't break our server

diff --git a/source/librpc/idl/krb5pac.idl b/source/librpc/idl/krb5pac.idl
index 3505fc895ce3c0f2faeef7347442624232e97444..b4509089154c8f2bab53503e23c430c4ebb13cbb 100644 (file)
--- a/source/librpc/idl/krb5pac.idl
+++ b/source/librpc/idl/krb5pac.idl
@@ -70,7 +70,11 @@ interface krb5pac
                [case(PAC_TYPE_SRV_CHECKSUM)]   PAC_SIGNATURE_DATA srv_cksum;
                [case(PAC_TYPE_KDC_CHECKSUM)]   PAC_SIGNATURE_DATA kdc_cksum;
                [case(PAC_TYPE_LOGON_NAME)]     PAC_LOGON_NAME logon_name;
-               [case(PAC_TYPE_UNKNOWN_12)]     [subcontext(0)] DATA_BLOB_REM unknown;
+               /* when new PAC info types are added they are supposed to be done
+                  in such a way that they are backwards compatible with existing
+                  servers. This makes it safe to just use a [default] for
+                  unknown types, which lets us ignore the data */
+               [default]       [subcontext(0)] DATA_BLOB_REM unknown;
                /* [case(PAC_TYPE_UNKNOWN_12)]  PAC_UNKNOWN_12 unknown; */
        } PAC_INFO;