Re: unzip failure with files that contain colons

[Andrey Repin <anrdaemon@yandex.ru>]

Greetings, Eliot Moss!

> On 6/16/2022 11:29 AM, Takashi Yano wrote:
>> On Thu, 16 Jun 2022 06:22:38 +0200
>> Thomas Wolff wrote:
>>> Am 15.06.2022 um 20:30 schrieb Adam Dinwoodie:
>>>> Cygwin generally handles filenames with colons just fine, by mapping the
>>>> character to some higher Unicode character and remapping on the fly.
>>>> However Cygwin's `unzip` appears to have a bug: when unzipping an
>>>> archive that contains a filename with a colon, it replaces the colon
>>>> with an underscore.
>>>>
>>>> cygcheck.out and simple test script attached; expected behaviour from
>>>> running `bash unzip-bug.sh` is that you get an empty file called `a:b`,
>>>> but on Cygwin you instead get an empty file called `a_b`.
>>> It's an explicit #ifdef __CYGWIN__ in upstream unzip, file unix/unix.c,
>>> which transforms a bunch of characters.
>>> If I uncomment most of them (except \), all unpack fine:
>>> x0:z  x1<z  x2>z  x3|z  x4"z  x5?z  x6*z
>> > I have taken over the maintenance of unzip package, and
>> fix the problem in the updated unzip-6.0-18.
>> https://cygwin.com/pipermail/cygwin/2022-June/251653.html

> Is colon used for ADS under Windows?  Could that be why one should
> be careful with it?

Colon is used (aside from being disk-path separator) as file stream indicator.
Replacing it is not strictly correct, in global sense of things, but unpacking
archives is not the place where you'd want to see data stored in multiple
streams.


-- 
With best regards,
Andrey Repin
Saturday, June 18, 2022 23:21:27

Sorry for my terrible english...