ZipArchive Reader: File name and comments should not be decoded using UTF8 if the general purpose bit 11 is not set in the header #285

Open
opened 2026-01-29 22:09:33 +00:00 by claunia · 0 comments
Owner

Originally created by @sridhar6668 on GitHub (Mar 27, 2018).

As per the zip format specification, If general purpose bit 11 is unset, the file name and comment should conform to the original ZIP character encoding(IBM PC character encoding set). Currently, the code always uses the UTF8 to decode the name and comment and it results in garbled strings if the name was encoded using IBM PC character encoding set.

Originally created by @sridhar6668 on GitHub (Mar 27, 2018). As per the zip format specification, If general purpose bit 11 is unset, the file name and comment should conform to the original ZIP character encoding(IBM PC character encoding set). Currently, the code always uses the UTF8 to decode the name and comment and it results in garbled strings if the name was encoded using IBM PC character encoding set.
claunia added the bug label 2026-01-29 22:09:33 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/sharpcompress#285