[cifs-protocol] [REG:119021819676760] Group Policy GPT.INI file encoding

Garming Sam garming at catalyst.net.nz
Mon Mar 4 21:45:53 UTC 2019


Attached is an example from Denis. (It seems to read 'New Group Policy
Object', so it looks like it even might be broken on the default
generated name)

The accented e appears to be at position E9 in the Latin-1 code page,
while the UTF-8 representation is supposed to be two bytes, C3 A9.



On 1/03/19 6:18 AM, Obaid Farooqi wrote:
> Hi Garming:
> Can you please send me a gpt.ini that has non-UTF8 characters?
> -----Original Message-----
> From: Obaid Farooqi 
> Sent: Tuesday, February 19, 2019 3:01 PM
> To: Garming Sam <garming at catalyst.net.nz>
> Cc: MSSolve Case Email <casemail at microsoft.com>; cifs-protocol at lists.samba.org; Denis CARDON <dcardon at tranquil.it>
> Subject: RE: [REG:119021819676760] Group Policy GPT.INI file encoding
> Hi Garming:
> I'll help you with this issue and will be in touch as soon as I have an answer.
> Regards,
> Obaid Farooqi
> Escalation Engineer | Microsoft 
> -----Original Message-----
> From: "Edgar Olougouna" <edgaro at microsoft.com> 
> Sent: Sunday, February 17, 2019 8:43 PM
> To: "Garming Sam" <garming at catalyst.net.nz>
> Cc: "MSSolve Case Email" <casemail at microsoft.com>; "cifs-protocol at lists.samba.org" <cifs-protocol at lists.samba.org>; "Denis CARDON" <dcardon at tranquil.it>
> Subject: [REG:119021819676760] Group Policy GPT.INI file encoding
> Hello Garming, Denis, 
> Glad to hear from you Denis. Thank you Garming for reaching out. 
> One of our team members will look into this and follow-up soon. 
> Thanks, 
> Edgar 
> -----Original Message----- 
> From: Garming Sam <garming at catalyst.net.nz> 
> Sent: Sunday, February 17, 2019 4:42 PM 
> To: Interoperability Documentation Help <dochelp at microsoft.com> 
> Cc: cifs-protocol at lists.samba.org; Denis CARDON <dcardon at tranquil.it> 
> Subject: Group Policy GPT.INI file encoding 
> Hi, 
> According to Denis, cc'd here, using a French RSAT appears to be
> writing GPT.INI files which are not UTF-8, but instead using ISO-8859 to
> represent accented characters (in the display name for a GPO).
> [MS-GPOL] 2.2.4 GPO Search 
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmsdn.
> microsoft.com%2Fen-us%2Flibrary%2Fcc232507.aspx&data=02%7C01%7C%7C6e1b1f
> a5c69d4f39b07008d6955b9580%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C
> 636860617932917342&sdata=y21TJvHpxyDDeE5nHJW8j1PL2Sk46BWe6lj%2FwjLQkCM%3
> D&reserved=0
> "The gpt.ini file MUST be encoded in UTF-8..." 
> According the the documentation, it is required to be UTF-8, so
> something doesn't quite add up here. Denis can probably reconfirm
> himself, but any assistance reproducing or confirming this behaviour
> would be appreciated. Assuming this is an issue, it's unclear what the
> effect of other locales is.
> Cheers, 
> Garming 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
URL: <http://lists.samba.org/pipermail/cifs-protocol/attachments/20190305/148353ea/GPT.ksh>

More information about the cifs-protocol mailing list