Re: [cifs-protocol] Status: SRX091111600231 [MS-ADA3]: 2.115 Structure of prefixMap over LDAP

2010-02-02 Thread Bill Wesse 
Glad to have been of assistance!

Regards,
Bill Wesse
MCSE, MCTS / Senior Escalation Engineer, US-CSS DSC PROTOCOL TEAM
8055 Microsoft Way
Charlotte, NC 28273
Email:  bil...@microsoft.com
Tel:+1(980) 776-8200
Cell:   +1(704) 661-5438
Fax:+1(704) 665-9606

-Original Message-
From: Kamen Mazdrashki [mailto:kamen.mazdras...@postpath.com] 
Sent: Monday, February 01, 2010 8:21 AM
To: Bill Wesse; abart...@samba.org
Cc: Obaid Farooqi; p...@tridgell.net; Sebastian Canevari; 
cifs-proto...@samba.org
Subject: RE: Status: SRX09600231 [MS-ADA3]: 2.115 Structure of prefixMap 
over LDAP

Thanks Bill,

Btw, we've implemented prefixMap over ldap dump handler and it works great.
Many thanks for publishing the format.

BR,
Kamen Mazdrashki
kamen.mazdras...@postpath.com
http://repo.or.cz/w/Samba/kamenim.git
-
CISCO SYSTEMS BULGARIA EOOD
http://www.cisco.com/global/BG/

 -Original Message-
 From: Bill Wesse [mailto:bil...@microsoft.com]
 Sent: Monday, February 01, 2010 3:14 PM
 To: abart...@samba.org; Kamen Mazdrashki
 Cc: Sebastian Canevari; Obaid Farooqi; p...@tridgell.net; cifs-
 proto...@samba.org
 Subject: RE: Status: SRX09600231 [MS-ADA3]: 2.115 Structure of
 prefixMap over LDAP
 
 Good morning again. Sebastian will be back in the office today; I have
 transferred case ownership back to him.
 
 Regards,
 Bill Wesse
 MCSE, MCTS / Senior Escalation Engineer, US-CSS DSC PROTOCOL TEAM
 8055 Microsoft Way
 Charlotte, NC 28273
 Email:bil...@microsoft.com
 Tel:  +1(980) 776-8200
 Cell: +1(704) 661-5438
 Fax:  +1(704) 665-9606
 
 
 -Original Message-
 From: Bill Wesse
 Sent: Thursday, January 28, 2010 11:46 AM
 To: 'abart...@samba.org'; 'kamen.mazdras...@postpath.com'
 Cc: Sebastian Canevari; Obaid Farooqi; 'p...@tridgell.net'; 'cifs-
 proto...@samba.org'
 Subject: Status: SRX09600231 [MS-ADA3]: 2.115 Structure of
 prefixMap over LDAP
 
 Good day Andrew  Kamen. Please note that my colleague Sebastian (who
 took ownership of this case from Obaid) is out of the office for the
 next few days.
 
 In the interim, I will be your contact. Thanks in advance for your
 patience!
 
 Andrew - I sent a status update request for the TDI (which has been in
 suspense since one of your previous emails (shown at the end of this
 message). I will advise you as soon as I receive a response.
 
 Kamen - I have already performed some investigation concerning those 20
 other prefixMap entries, and expect to follow up with your tomorrow
 morning.
 
 Regards,
 Bill Wesse
 MCSE, MCTS / Senior Escalation Engineer, US-CSS DSC PROTOCOL TEAM
 8055 Microsoft Way
 Charlotte, NC 28273
 Email:bil...@microsoft.com
 Tel:  +1(980) 776-8200
 Cell: +1(704) 661-5438
 Fax:  +1(704) 665-9606
 
 -Original Message-
 From: Kamen Mazdrashki [mailto:kamen.mazdras...@postpath.com]
 Sent: Friday, January 15, 2010 3:09 AM
 To: Obaid Farooqi; abart...@samba.org
 Cc: p...@tridgell.net; cifs-proto...@samba.org
 Subject: RE: [cifs-protocol] Structure of prefixMap over LDAP
 
 Hi Obaid,
 
 Could you please point out where those default 39 entries for prefixMap
 are described?
 I am looking at: http://msdn.microsoft.com/en-
 us/library/cc228445%28PROT.13%29.aspx
 and there are only 19 default prefixes listed here.
 
 
 
 Thanks,
 Kamen Mazdrashki
 kamen.mazdras...@postpath.com mailto:kamen.mazdras...@postpath.com
 http://repo.or.cz/w/Samba/kamenim.git
 -
 CISCO SYSTEMS BULGARIA EOOD
 http://www.cisco.com/global/BG/
 
 -Original Message-
 From: Andrew Bartlett [mailto:abart...@samba.org]
 Sent: Tuesday, December 15, 2009 1:39 AM
 To: Obaid Farooqi
 Cc: cifs-proto...@samba.org; p...@tridgell.net
 Subject: RE: Structure of prefixMap over LDAP
 
 On Tue, 2009-12-15 at 06:22 +, Obaid Farooqi wrote:
  Hi Andrew:
  In an effort to fully understand your goals, please explain what you
  are looking  to achieve through the addition of documentation that
  defines the internal structure of the prefixMap attribute.
 
 As a start:
 
 The ability to generate a matching prefixMap attribute, should any
 client request it.  The ability to verify prefixMap values over DRS and
 LDAP to confirm consistency.  The ability to include prefixMap values
 in comparison tests we may make between AD and Samba4.  An
 understanding of how the contents of this attribute interacts with
 msDs-intID and other prefix mapping functionality.
 
 Finally, I'm simply looking to ensure that the documentation set
 explains the format of every value (generated or otherwise) in AD, so
 we don't have to come back to this later.
 
 Thanks,
 
 Andrew Bartlett
 
 --
 Andrew Bartlett
 http://samba.org/~abartlet/
 Authentication Developer, Samba Team   http://samba.org
 Samba Developer, Cisco Inc.


___
cifs-protocol mailing list
cifs-protocol@cifs.org
https://lists.samba.org/mailman/listinfo/cifs-protocol

[cifs-protocol] [Pfif] CAR: Bad variable names in MS-RPRN : 3.1.4.1.2 Dynamically Typed Query Parameters

2010-02-02 Thread Jeremy Allison 
Dear Dochelp,

In MS-RPRN, section : 3.1.4.1.2 Dynamically Typed Query Parameters.

the text reads:


3.1.4.1.2 Dynamically Typed Query Parameters

Unless notified otherwise, methods returning one or more dynamically-typed 
values use a common
API pattern, in which the caller passes in the following parameters:

BUFFER: A buffer into which the server copies the requested dynamically-typed 
values. The term
BUFFER is used here as a placeholder. Each method section defines which of 
its parameters is
the pointer to the buffer.

pType: An optional pointer to a variable that receives a code that indicates 
the type of data that
is stored in the specified value. For a list of possible type values, see 
section 2.2.3.9.

nSize or cbData: The size, in bytes, of the buffer. This value can be larger 
than the required size
for the requested dynamically-typed values.

pcbNeeded or pcbData: A pointer to a variable into which the server copies the 
number of bytes
between the start of BUFFER and the last byte written by the server into 
BUFFER, both inclusive;
or the required size of the buffer, in bytes, if the value of cbBuf is smaller 
than the size of the
data to return to the caller. For methods capable of returning more than one 
dynamically-typed
value, the caller also passes in:

pcReturned: A pointer to a variable into which the server copies the number of 
dynamically-typed
values that were written to the buffer, if the buffer was large enough to hold 
them.

The individual method sections include the following parameter validation steps 
by reference:
The server MUST verify that the value of cbBuf is not smaller than the number 
of bytes required
to hold the dynamically-typed values to be written to the buffer.

If that verification fails, the server MUST write the number of bytes required 
into the variable
that is pointed to by pcbNeeded and return ERROR_MORE_DATA.

If the value of cbBuf is not zero, the server MUST verify that a non-NULL 
pointer to the buffer
was passed in. If that verification fails, the server MUST return 
ERROR_INVALID_USER_BUFFER.


I believe the references to the variable name cbBuf in the above are
incorrect, and should be replaced with nSize or with cbData.

There is no variable name cbBuf defined in this section. It appears to
be a cut-and-paste error from 3.1.4.1.7 String Query Parameters, which
does define the cbBuf variable name.

Please let me know if this is correct.

Thanks,

Jeremy.
___
cifs-protocol mailing list
cifs-protocol@cifs.org
https://lists.samba.org/mailman/listinfo/cifs-protocol