From 2ca65a99c77d6d119617c330ce521a6137d71e35 Mon Sep 17 00:00:00 2001 From: Andrew Tridgell Date: Sat, 22 Nov 2003 01:27:40 +0000 Subject: added some explanations for epmapper IDL and dom_sid2 (This used to be commit 5962f1cffa9273cc06c8a3c4a112f3ce94b84dae) --- source4/librpc/ndr/ndr_sec.h | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) (limited to 'source4/librpc/ndr/ndr_sec.h') diff --git a/source4/librpc/ndr/ndr_sec.h b/source4/librpc/ndr/ndr_sec.h index 27a1311adc..728d46535d 100644 --- a/source4/librpc/ndr/ndr_sec.h +++ b/source4/librpc/ndr/ndr_sec.h @@ -22,7 +22,17 @@ */ -/* use the same structure for dom_sid2 as dom_sid */ +/* + use the same structure for dom_sid2 as dom_sid. A dom_sid2 is really + just a dom sid, but with the sub_auths represented as a conformant + array. As with all in-structure conformant arrays, the array length + is placed before the start of the structure. That's what gives rise + to the extra num_auths elemenent. We don't want the Samba code to + have to bother with such esoteric NDR details, so its easier to just + define it as a dom_sid and use pidl magic to make it all work. It + just means you need to mark a sid as a "dom_sid2" in the IDL when you + know it is of the conformant array variety +*/ #define dom_sid2 dom_sid /* query security descriptor */ -- cgit