Andrew, Matthieu,
I noticed that Matthieu updated the LDAP representation blob and the SAMR
network capture that shows the UTF16 string in SamrSetInformationUser in the
bug (https://bugzilla.samba.org/show_bug.cgi?id=8077). Could you tell us
the exact steps you used to do the testing ? The product team needs that to
have the same repro for the investigation.
Thanks!
Hongwei
-----Original Message-----
From: Andrew Bartlett [mailto:[email protected]]
Sent: Monday, June 20, 2011 8:09 PM
To: Hongwei Sun
Cc: Stefan (metze) Metzmacher; [email protected]; [email protected];
Michael Ströder
Subject: RE: [REG: 111052361876778] RE: userParameters attribute
On Mon, 2011-06-20 at 20:14 +0000, Hongwei Sun wrote:
> Metze/Andrew,
>
> We updated the description of userParameters in MS-ADA3 and other related
> documents to clarify that it is not saved as utf16 or utf8 Unicode strings as
> below. They will appear in the next release of the open protocol documents.
The key point that seems to be brushed over here is: how is this 'not UTF8'
string in LDAP translated into and from the representation sent over SAMR
(which appears to be UTF16)?
For example, please explain how the values seen in this bug get translated
between each other. At a first glance, the translation does indeed appear to
be that between UTF16 and UTF8, so if they are not
UTF16 and UTF8 strings, what are they, and what defines the translation?
https://bugzilla.samba.org/show_bug.cgi?id=8077
Andrew Bartlett
--
Andrew Bartlett http://samba.org/~abartlet/
Authentication Developer, Samba Team http://samba.org
_______________________________________________
cifs-protocol mailing list
[email protected]
https://lists.samba.org/mailman/listinfo/cifs-protocol
