summaryrefslogtreecommitdiff
path: root/source3
diff options
context:
space:
mode:
authorAndrew Tridgell <tridge@samba.org>2008-08-24 14:00:58 +1000
committerMichael Adam <obnox@samba.org>2008-08-26 15:07:29 +0200
commit5b851c93bd318edd34bd24e3033d45b769c8c36c (patch)
tree9b1cadd96157b17cf9bfb10230d8b6a7c6eed63e /source3
parent39697d57451d05585063dc05c4fd6c5ae646a0a5 (diff)
downloadsamba-5b851c93bd318edd34bd24e3033d45b769c8c36c.tar.gz
samba-5b851c93bd318edd34bd24e3033d45b769c8c36c.tar.bz2
samba-5b851c93bd318edd34bd24e3033d45b769c8c36c.zip
Handle arbitrary new PAC types
When MS introduces a new PAC type, we should just ignore it, not generate a parse error. New PAC info structures are supposed to be backwards compatible with old ones (This used to be commit 2971b926c835412b02c93ad1e30f1471bc0a3612)
Diffstat (limited to 'source3')
-rw-r--r--source3/librpc/idl/krb5pac.idl2
1 files changed, 1 insertions, 1 deletions
diff --git a/source3/librpc/idl/krb5pac.idl b/source3/librpc/idl/krb5pac.idl
index 7c2f72d3cb..c039502d23 100644
--- a/source3/librpc/idl/krb5pac.idl
+++ b/source3/librpc/idl/krb5pac.idl
@@ -70,7 +70,7 @@ 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;
+ [default] [subcontext(0)] DATA_BLOB_REM unknown;
/* [case(PAC_TYPE_UNKNOWN_12)] PAC_UNKNOWN_12 unknown; */
} PAC_INFO;