[cifs-protocol] [EXTERNAL] [MS-XCA] LZ77+ Huffman example 1 - TrackingID#2210140040005999
Jeff McCashland (He/him)
jeffm at microsoft.com
Fri Oct 14 20:56:01 UTC 2022
[Tom to BCC]
I will look into this question and let you know what I find.
Jeff McCashland (He/him) | Senior Escalation Engineer | Microsoft Protocol Open Specifications Team
Phone: +1 (425) 703-8300 x38300 | Hours: 9am-5pm | Time zone: (UTC-08:00) Pacific Time (US and Canada)
Local country phone number found here: http://support.microsoft.com/globalenglish | Extension 1138300
From: Tom Jebo <tomjebo at microsoft.com>
Sent: Friday, October 14, 2022 9:41 AM
To: Douglas Bagnall <douglas.bagnall at catalyst.net.nz>; cifs-protocol at lists.samba.org; Aurélien Aptel <aaptel at suse.com>; Samuel Cabrero (Samba) <scabrero at samba.org>
Cc: Microsoft Support <supportmail at microsoft.com>
Subject: RE: [EXTERNAL] [MS-XCA] LZ77+ Huffman example 1 - TrackingID#2210140040005999
[dochelp to bcc]
Thank you for your request. One of the Open Specifications team will respond to start working with you. I have created case 2210140040005999 and added the number to the subject of this email. Please refer to this case number in future communications regarding this issue.
Sr Escalation Engineer
Microsoft Open Specifications
From: Douglas Bagnall <douglas.bagnall at catalyst.net.nz>
Sent: Thursday, October 13, 2022 9:35 PM
To: Interoperability Documentation Help <dochelp at microsoft.com>; cifs-protocol at lists.samba.org; Aurélien Aptel <aaptel at suse.com>; Samuel Cabrero (Samba) <scabrero at samba.org>
Subject: [EXTERNAL] [MS-XCA] LZ77+ Huffman example 1
In the first example in Section 3.2, where "abcdefghijklmnopqrstuvwxyz" is "compressed" into a ~282 byte sequence ending with
d8 52 3e d7 94 11 5b e9 19 5f f9 d6 7c df 8d 04 00 00 00 00
where do all the trailing zeros come from?
They do not encode characters, and from the decoding description in 2.2.4, we don't read 32 bits at a time except at the start of the first block, so processing should be well finished before we get to read these. It seems to violate the "input buffer is finished" termination rule.
More information about the cifs-protocol