<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Activity for Info-ZIP project</title><link>https://sourceforge.net/p/infozip/activity/</link><description>Recent activity for Info-ZIP project</description><language>en</language><lastBuildDate>Thu, 23 Apr 2026 15:08:16 -0000</lastBuildDate><item><title>Paul Marquess posted a comment on ticket #86</title><link>https://sourceforge.net/p/infozip/bugs/86/?limit=25#de6b</link><description>Very nice bug report Nicholas Unfortunately, I'm not seeing this is a valid issue that unzip should do anything about. Here is a real life example that I don't think is unique to my workflow: I have a shortcut to my development directory tree setup as a symbolic link -- so something like ~/my-code will actually point to the real path where my dev code lives. If I want unzip some content into my development tree, I would write this unzip myzip.zip -d ~/my-code or this unzip myzip.zip -d ~/my-code/new-files...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul Marquess</dc:creator><pubDate>Thu, 23 Apr 2026 15:08:16 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/86/?limit=25#de6b</guid></item><item><title>Nicholas Wei created ticket #86</title><link>https://sourceforge.net/p/infozip/bugs/86/</link><description>Info-ZIP UnZip below 6.10b BETA — Arbitrary File Write via Preexisting Destination Symlinks</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Nicholas Wei</dc:creator><pubDate>Thu, 23 Apr 2026 06:31:24 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/86/</guid></item><item><title>Paul Marquess posted a comment on ticket #85</title><link>https://sourceforge.net/p/infozip/bugs/85/?limit=25#0bd8</link><description>Hey Ronish variations on this issue has been around for a while, but thanks for taking the time to formalise it in a ticket. Last one I heard of was embedding a complete zip file in the trailing zip comment. A use-case where this could be used is where the unzipping code works in streaming mode and walks the local directory entries in turn without bothering about the Central Dirsctory &amp; EOCD. In that case, the standard commandline tools would think this was a zip file with zero entries, but the streaming...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul Marquess</dc:creator><pubDate>Tue, 24 Mar 2026 17:51:31 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/85/?limit=25#0bd8</guid></item><item><title>Ronish Bhatt created ticket #85</title><link>https://sourceforge.net/p/infozip/bugs/85/</link><description>Trailing Fake EOCD Causes Archive to be Interpreted as Empty in unzip 6.0</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ronish Bhatt</dc:creator><pubDate>Tue, 24 Mar 2026 15:09:00 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/85/</guid></item><item><title>林博仁(Buo-ren Lin) created ticket #84</title><link>https://sourceforge.net/p/infozip/bugs/84/</link><description>Manpages are no longer accessible from the website.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">林博仁(Buo-ren Lin)</dc:creator><pubDate>Sat, 14 Feb 2026 06:59:03 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/84/</guid></item><item><title>Paul Marquess posted a comment on ticket #83</title><link>https://sourceforge.net/p/infozip/bugs/83/?limit=25#3d80</link><description>Thanks for taking the time to provide a patch for TIME_T_TYPE_DOUBLE. Confirmed that building the unzip 6.0 source with -DTIME_T_TYPE_DOUBLE does trigger a number of compilation issues. Although your patch does silence them, I see that the updates to the development source for unzip appear to have a fix for this issue -- it builds with any compilation errors. . With a very superficial look at the sources, I suspect your's my be the correct change. Won't know for sure until I run a few tests. One...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul Marquess</dc:creator><pubDate>Sat, 09 Aug 2025 12:34:31 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/83/?limit=25#3d80</guid></item><item><title>Taketo Kabe created ticket #83</title><link>https://sourceforge.net/p/infozip/bugs/83/</link><description>unzip cannot be compiled with -DTIME_T_TYPE_DOUBLE=1 to make it Y2038 compliant on 32bit</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Taketo Kabe</dc:creator><pubDate>Sat, 09 Aug 2025 09:19:36 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/83/</guid></item><item><title>Steven Schweda posted a comment on ticket #20</title><link>https://sourceforge.net/p/infozip/support-requests/20/?limit=25#6fe8</link><description>On Win 10 ( 32 bit ) computer ... Ok. Use WinRAR to decompress ... Not our program. Not our problem. Still more questions than answers. For example: "After decompression" of what? How was your (invisible) zip archive created? How do you know that there are ".exe" files in your original folder? How do you know that there are ".exe" files in your archive? Even if you were using our software, you would still need to provide some basic information, and you have not done that.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Steven Schweda</dc:creator><pubDate>Fri, 18 Jul 2025 02:54:54 -0000</pubDate><guid>https://sourceforge.net/p/infozip/support-requests/20/?limit=25#6fe8</guid></item><item><title>Paul Marquess posted a comment on ticket #20</title><link>https://sourceforge.net/p/infozip/support-requests/20/?limit=25#1ecb</link><description>WinRAR is off-topic for this list. This forum is only for the Info-ZIP zip &amp; unzip programs. It doesn't cover WinRAR Try uncompressing with unzip or 7z. If it fails with unzip, ask here again.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul Marquess</dc:creator><pubDate>Thu, 17 Jul 2025 12:51:22 -0000</pubDate><guid>https://sourceforge.net/p/infozip/support-requests/20/?limit=25#1ecb</guid></item><item><title>xx xxx posted a comment on ticket #20</title><link>https://sourceforge.net/p/infozip/support-requests/20/?limit=25#1c8d</link><description>On Win 10 ( 32 bit ) computer ... Use WinRAR to decompress ... .</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">xx xxx</dc:creator><pubDate>Thu, 17 Jul 2025 05:06:21 -0000</pubDate><guid>https://sourceforge.net/p/infozip/support-requests/20/?limit=25#1c8d</guid></item><item><title>Steven Schweda posted a comment on ticket #20</title><link>https://sourceforge.net/p/infozip/support-requests/20/?limit=25#adba</link><description>&gt; After decompression ... &gt; No .exe file was found on the decompressed folder ... Before anyone can help you, you will need to provide some basic information about your environment(s), what you did, and what happened when you did it. Hardware? Software? OS/version? zip -v unzip -v Actual commands? Actual results? Copy+paste is your friend. "After decompression" of _what_? How was your (invisible) zip archive created? How do you know that there are ".exe" files in your original folder? How do you...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Steven Schweda</dc:creator><pubDate>Sat, 12 Jul 2025 03:19:25 -0000</pubDate><guid>https://sourceforge.net/p/infozip/support-requests/20/?limit=25#adba</guid></item><item><title>xx xxx created ticket #20</title><link>https://sourceforge.net/p/infozip/support-requests/20/</link><description>After decompression ...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">xx xxx</dc:creator><pubDate>Fri, 11 Jul 2025 22:44:55 -0000</pubDate><guid>https://sourceforge.net/p/infozip/support-requests/20/</guid></item><item><title>Santiago Vila created ticket #82</title><link>https://sourceforge.net/p/infozip/bugs/82/</link><description>zip: support for cross-compilation and large file support</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Santiago Vila</dc:creator><pubDate>Tue, 22 Apr 2025 23:04:56 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/82/</guid></item><item><title>Santiago Vila created ticket #81</title><link>https://sourceforge.net/p/infozip/bugs/81/</link><description>zip: Two bugfixes and a dep8 test</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Santiago Vila</dc:creator><pubDate>Tue, 22 Apr 2025 22:57:21 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/81/</guid></item><item><title>Santiago Vila created ticket #80</title><link>https://sourceforge.net/p/infozip/bugs/80/</link><description>zip: Sets 'version needed to extract' to 1.0 even if there are deflated files</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Santiago Vila</dc:creator><pubDate>Tue, 22 Apr 2025 22:49:40 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/80/</guid></item><item><title>Santiago Vila created ticket #79</title><link>https://sourceforge.net/p/infozip/bugs/79/</link><description>zip: Charset conversion fails when zip is built with _FORTIFY_SOURCE</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Santiago Vila</dc:creator><pubDate>Tue, 22 Apr 2025 22:43:37 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/79/</guid></item><item><title>Santiago Vila created ticket #78</title><link>https://sourceforge.net/p/infozip/bugs/78/</link><description>zip: fails to delete file from archive</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Santiago Vila</dc:creator><pubDate>Tue, 22 Apr 2025 22:36:49 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/78/</guid></item><item><title>Santiago Vila created ticket #77</title><link>https://sourceforge.net/p/infozip/bugs/77/</link><description>zipnote: Segfault during write operation</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Santiago Vila</dc:creator><pubDate>Tue, 22 Apr 2025 22:29:28 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/77/</guid></item><item><title>Santiago Vila created ticket #76</title><link>https://sourceforge.net/p/infozip/bugs/76/</link><description>zip: UTF-8 GPBF bit 11 is not set if "en_US.UTF-8" locale is not available</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Santiago Vila</dc:creator><pubDate>Tue, 22 Apr 2025 22:22:58 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/76/</guid></item><item><title>Santiago Vila created ticket #75</title><link>https://sourceforge.net/p/infozip/bugs/75/</link><description>zip: CVE-2018-13410</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Santiago Vila</dc:creator><pubDate>Tue, 22 Apr 2025 22:17:11 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/75/</guid></item><item><title>Santiago Vila created ticket #74</title><link>https://sourceforge.net/p/infozip/bugs/74/</link><description>--filesync is incompatible with --symlinks (symliks are always updated)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Santiago Vila</dc:creator><pubDate>Tue, 22 Apr 2025 18:42:25 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/74/</guid></item><item><title>Cálestyo created ticket #9</title><link>https://sourceforge.net/p/infozip/feature-requests/9/</link><description>add option to return a non-zero exit staus if -n was used and a file couldn't be extracted</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Cálestyo</dc:creator><pubDate>Thu, 20 Mar 2025 01:40:59 -0000</pubDate><guid>https://sourceforge.net/p/infozip/feature-requests/9/</guid></item><item><title>tom235 posted a comment on ticket #42</title><link>https://sourceforge.net/p/infozip/bugs/42/?limit=25#0f8b</link><description>it would be great if after a decade now we could apply this patch here ;-) WDYT?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">tom235</dc:creator><pubDate>Mon, 09 Dec 2024 23:38:00 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/42/?limit=25#0f8b</guid></item><item><title>unxed posted a comment on ticket #43</title><link>https://sourceforge.net/p/infozip/bugs/43/?limit=25#241c</link><description>Similar fix suggested for Ubuntu's unzip: https://code.launchpad.net/~mitya57/ubuntu/+source/unzip/+git/unzip/+merge/466860</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">unxed</dc:creator><pubDate>Sat, 08 Jun 2024 22:19:12 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/43/?limit=25#241c</guid></item><item><title>Paul Marquess posted a comment on ticket #19</title><link>https://sourceforge.net/p/infozip/support-requests/19/?limit=25#7c29/f1d3</link><description>Comparing the first zipinfo listing with the most recent, the differences are the following fields offset of local header from start of archive minimum software version required to extract 32-bit CRC value (hex) compressed size uncompressed size All but the "minimum software version required to extract" you would expect to change if you've modified the file. The " minimum software version required to extract" has changed from 2.0 to 1.0, so I assume that is the one you are concerned with. classes5.dex...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul Marquess</dc:creator><pubDate>Thu, 06 Jun 2024 10:29:10 -0000</pubDate><guid>https://sourceforge.net/p/infozip/support-requests/19/?limit=25#7c29/f1d3</guid></item><item><title>Alex Mihail posted a comment on ticket #19</title><link>https://sourceforge.net/p/infozip/support-requests/19/?limit=25#7c29</link><description>I guess it has become an episode of "how do I recreate this original file" more than anything being "wrong" per se. Let me illustrate it better. Here's the zipinfo -v of the classes.dex files inside a framework.jar - they are created with this "metadata" Central directory entry #53: --------------------------- classes5.dex offset of local header from start of archive: 39838572 (00000000025FE36Ch) bytes file system or operating system of origin: Unix version of encoding software: 2.0 minimum file...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alex Mihail</dc:creator><pubDate>Thu, 06 Jun 2024 09:59:39 -0000</pubDate><guid>https://sourceforge.net/p/infozip/support-requests/19/?limit=25#7c29</guid></item><item><title>Steven Schweda posted a comment on ticket #19</title><link>https://sourceforge.net/p/infozip/support-requests/19/?limit=25#5ade</link><description>[...] which looks to me like a bug, [...] CHANGES says that this was fixed in Zip version 3.1d03. Current development code (3.1e23) works correctly.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Steven Schweda</dc:creator><pubDate>Thu, 06 Jun 2024 03:51:40 -0000</pubDate><guid>https://sourceforge.net/p/infozip/support-requests/19/?limit=25#5ade</guid></item><item><title>Steven Schweda posted a comment on ticket #19</title><link>https://sourceforge.net/p/infozip/support-requests/19/?limit=25#91b6</link><description>[...] requiring a minimum version of Zip 2.0 to extract ... however, I cannot seem to find this version existing anywhere, [...] So what? Which part of "minimum" is unclear to you? According to the APPNOTE: https://pkware.cachefly.net/webdocs/casestudies/APPNOTE.TXT Version Needed To Extract = 2.0 for an archive member means that one of the following features was used: File is a folder (directory) File is compressed using Deflate compression File is encrypted using traditional PKWARE encryption I...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Steven Schweda</dc:creator><pubDate>Wed, 05 Jun 2024 22:49:01 -0000</pubDate><guid>https://sourceforge.net/p/infozip/support-requests/19/?limit=25#91b6</guid></item><item><title>Paul Marquess posted a comment on ticket #19</title><link>https://sourceforge.net/p/infozip/support-requests/19/?limit=25#f680</link><description>The term "version needed to extract" refers to the version of the zip specification and not the version of any zip/unzip implementation. See section 4.4.3.1 of APPNOTE.txt at https://pkwaredownloads.blob.core.windows.net/pem/APPNOTE.txt for the details. That then means you just need an unzip implementation that supports version 2 or better of the APPNOTE.txt specification. I'm not aware of any unzip implementation that doesn't support version 2 of the spec (which was written in the early 1990s) If...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul Marquess</dc:creator><pubDate>Wed, 05 Jun 2024 19:44:15 -0000</pubDate><guid>https://sourceforge.net/p/infozip/support-requests/19/?limit=25#f680</guid></item><item><title>Alex Mihail created ticket #19</title><link>https://sourceforge.net/p/infozip/support-requests/19/</link><description>Zip 2.0?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alex Mihail</dc:creator><pubDate>Wed, 05 Jun 2024 18:51:31 -0000</pubDate><guid>https://sourceforge.net/p/infozip/support-requests/19/</guid></item><item><title>unxed posted a comment on ticket #45</title><link>https://sourceforge.net/p/infozip/bugs/45/?limit=25#798b/629c</link><description>The patch itself</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">unxed</dc:creator><pubDate>Fri, 31 May 2024 21:55:09 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/45/?limit=25#798b/629c</guid></item><item><title>Paul Marquess posted a comment on ticket #73</title><link>https://sourceforge.net/p/infozip/bugs/73/?limit=25#9c17</link><description>Thanks for the bug report! The Red Hat fix is present in the development version of zip.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul Marquess</dc:creator><pubDate>Wed, 29 May 2024 16:16:05 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/73/?limit=25#9c17</guid></item><item><title>newhoa created ticket #73</title><link>https://sourceforge.net/p/infozip/bugs/73/</link><description>zip fails with non-latin unicode</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">newhoa</dc:creator><pubDate>Mon, 27 May 2024 17:23:25 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/73/</guid></item><item><title>unxed posted a comment on ticket #43</title><link>https://sourceforge.net/p/infozip/bugs/43/?limit=25#2066</link><description>Debian's 7zip just merged a fix for the same problem: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779207#51</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">unxed</dc:creator><pubDate>Wed, 22 May 2024 20:34:10 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/43/?limit=25#2066</guid></item><item><title>Paul Marquess posted a comment on ticket #43</title><link>https://sourceforge.net/p/infozip/bugs/43/?limit=25#0318</link><description>There is a patched version of unzip that some of the Linux distros ship that allows the codepage/encoding to be specified. That deals with this use-case. In this case, , specifying codepage 866 with the -O option does the trick $ unzip -l -O cp866 Desktop.zip Archive: Desktop.zip Length Date Time Name --------- ---------- ----- ---- 0 09-28-2016 18:41 Новая папка/ 4 09-28-2016 18:40 Новый текстовый документ.txt --------- ------- 4 2 files</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul Marquess</dc:creator><pubDate>Wed, 22 May 2024 15:26:48 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/43/?limit=25#0318</guid></item><item><title>Paul Marquess posted a comment on ticket #43</title><link>https://sourceforge.net/p/infozip/bugs/43/?limit=25#951c/2bf8</link><description>It looks like codepage 866, i.e. Cyrillic</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul Marquess</dc:creator><pubDate>Wed, 22 May 2024 15:20:26 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/43/?limit=25#951c/2bf8</guid></item><item><title>Paul Marquess posted a comment on ticket #43</title><link>https://sourceforge.net/p/infozip/bugs/43/?limit=25#951c/878d</link><description>What encoding is used for the filenames in Desktop.zip?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul Marquess</dc:creator><pubDate>Wed, 22 May 2024 15:13:05 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/43/?limit=25#951c/878d</guid></item><item><title>unxed modified a comment on ticket #43</title><link>https://sourceforge.net/p/infozip/bugs/43/?limit=25#951c</link><description>The built-in .zip archiver in older versions of Windows used DOS (OEM) or Windows (ANSI) code page corresponding to current regional settings for new archives. Lots of such archives still exist. The correct behavior is to determine the relevant OEM or ANSI code page based on the system locale and use it. You can look at this PR for reference implementation: https://github.com/p7zip-project/p7zip/pull/232 Sample archive showing this bug attached.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">unxed</dc:creator><pubDate>Wed, 22 May 2024 14:56:42 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/43/?limit=25#951c</guid></item><item><title>unxed posted a comment on ticket #43</title><link>https://sourceforge.net/p/infozip/bugs/43/?limit=25#951c</link><description>The built-in .zip archiver in older versions of Windows used DOS (OEM) or Windows (ANSI) code page corresponding to current regional settings for new archives. Lots of such archives still exist. The correct behavior is to determine the relevant OEM or ANSI code page based on the system locale and use it. You can look at this PR for reference implementation: https://github.com/p7zip-project/p7zip/pull/232</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">unxed</dc:creator><pubDate>Wed, 22 May 2024 14:55:05 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/43/?limit=25#951c</guid></item><item><title>Paul Marquess posted a comment on ticket #72</title><link>https://sourceforge.net/p/infozip/bugs/72/?limit=25#912a/ecb7/55f7/c2e3/e9a6</link><description>Ta. I'll wait for the official gcc 14.1 &amp; see if I can reproduce the error</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul Marquess</dc:creator><pubDate>Thu, 02 May 2024 10:49:09 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/72/?limit=25#912a/ecb7/55f7/c2e3/e9a6</guid></item><item><title>Rudi Heitbaum posted a comment on ticket #72</title><link>https://sourceforge.net/p/infozip/bugs/72/?limit=25#912a/ecb7/55f7/c2e3</link><description>This is on the development branch of LibreELEC (version 13.0) (Linux 6.6.29) and with gcc-14.1rc. I will be updating the dev branch to gcc 14.1 once it is formally released,.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rudi Heitbaum</dc:creator><pubDate>Thu, 02 May 2024 10:18:28 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/72/?limit=25#912a/ecb7/55f7/c2e3</guid></item><item><title>Paul Marquess posted a comment on ticket #72</title><link>https://sourceforge.net/p/infozip/bugs/72/?limit=25#912a/ecb7/55f7</link><description>Thanks Should have asked upfront, but what platform &amp; C compiler are you running?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul Marquess</dc:creator><pubDate>Thu, 02 May 2024 09:49:45 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/72/?limit=25#912a/ecb7/55f7</guid></item><item><title>Rudi Heitbaum posted a comment on ticket #72</title><link>https://sourceforge.net/p/infozip/bugs/72/?limit=25#912a/ecb7</link><description>Hi Paul, without time.h - this is the error: timezone.c: In function 'mktime': timezone.c:644:18: error: invalid use of undefined type 'struct tm' 644 | save_isdst = tm-&gt;tm_isdst; | ^~ timezone.c:647:7: error: invalid use of undefined type 'struct tm' 647 | tm-&gt;tm_isdst = save_isdst; | ^~ timezone.c:661:11: error: implicit declaration of function 'localtime' [-Wimplicit-function-declaration] 661 | ltm = localtime(&amp;then); | ^~~~~~~~~ timezone.c:44:1: note: 'localtime' is defined in header '&lt;time.h&gt;';...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rudi Heitbaum</dc:creator><pubDate>Thu, 02 May 2024 09:46:44 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/72/?limit=25#912a/ecb7</guid></item><item><title>Paul Marquess posted a comment on ticket #72</title><link>https://sourceforge.net/p/infozip/bugs/72/?limit=25#1042</link><description>Thanks Rudi. The changes to configure match ones we've already applied.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul Marquess</dc:creator><pubDate>Wed, 01 May 2024 12:46:40 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/72/?limit=25#1042</guid></item><item><title>Paul Marquess posted a comment on ticket #72</title><link>https://sourceforge.net/p/infozip/bugs/72/?limit=25#912a</link><description>What error did you get that meant that you had to add #include &lt;time.h&gt; to timezone.c?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul Marquess</dc:creator><pubDate>Wed, 01 May 2024 12:44:49 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/72/?limit=25#912a</guid></item><item><title>Rudi Heitbaum created ticket #72</title><link>https://sourceforge.net/p/infozip/bugs/72/</link><description>patch to compile with gcc-14.1</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rudi Heitbaum</dc:creator><pubDate>Wed, 01 May 2024 12:26:19 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/72/</guid></item><item><title>Takashi Yano posted a comment on ticket #30</title><link>https://sourceforge.net/p/infozip/patches/30/?limit=25#aafc</link><description>Cygwin replaces these chars with unicode chars of 0xf000 | ch. Therefore, cygwin can treat these chars as a part of filename. Of course, they cannot be displayed properly outside cygwin.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Takashi Yano</dc:creator><pubDate>Wed, 24 Apr 2024 17:18:38 -0000</pubDate><guid>https://sourceforge.net/p/infozip/patches/30/?limit=25#aafc</guid></item><item><title>Sam Tansy posted a comment on ticket #30</title><link>https://sourceforge.net/p/infozip/patches/30/?limit=25#2084</link><description>How do you want to create such files in windows?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Sam Tansy</dc:creator><pubDate>Mon, 22 Apr 2024 13:48:52 -0000</pubDate><guid>https://sourceforge.net/p/infozip/patches/30/?limit=25#2084</guid></item><item><title>Paul Marquess posted a comment on ticket #71</title><link>https://sourceforge.net/p/infozip/bugs/71/?limit=25#bfb9</link><description>I note that all of the issues listed have been addressed downstream by the main Linux distributions. Not necessarily all of them in each of the distributions, but at least there are fixes available. I have a couple of GH repos that have tried to collect all the variations of zip &amp; unzip that are out in the wild. By no means complete, but it does show the fragmentation that has happened over the last few years. See nfo-ZIP-Family-Tree-for-Zip and nfo-ZIP-Family-Tree-for-UnZip) for more details. Having...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul Marquess</dc:creator><pubDate>Mon, 16 Oct 2023 13:46:08 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/71/?limit=25#bfb9</guid></item><item><title>Neustradamus posted a comment on ticket #71</title><link>https://sourceforge.net/p/infozip/bugs/71/?limit=100#0ba7</link><description>Dear @infozip team, @antinode2, @eewhite, @goathunter, @gordone, @roelofs, Can you answer to @allwit and me. There are a lot of CVEs never patched. In more, it will be nice to have an official InfoZip GitHub organization to contribute etc. Thanks in advance. Regards.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Neustradamus</dc:creator><pubDate>Fri, 13 Oct 2023 22:51:03 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/71/?limit=100#0ba7</guid></item><item><title>Neustradamus posted a comment on ticket #8</title><link>https://sourceforge.net/p/infozip/feature-requests/8/?limit=100#2906</link><description>Dear @infozip team, @antinode2, @eewhite, @goathunter, @gordone, @roelofs, Can you answer to @kloczek and me. It is about all files and more: - https://sourceforge.net/projects/infozip/files/ Thanks in advance. Regards.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Neustradamus</dc:creator><pubDate>Fri, 13 Oct 2023 22:46:47 -0000</pubDate><guid>https://sourceforge.net/p/infozip/feature-requests/8/?limit=100#2906</guid></item><item><title>Peyton Zhong created ticket #71</title><link>https://sourceforge.net/p/infozip/bugs/71/</link><description>when the next version 6.1 will be released</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Peyton Zhong</dc:creator><pubDate>Tue, 27 Jun 2023 02:38:27 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/71/</guid></item><item><title>miskox created ticket #18</title><link>https://sourceforge.net/p/infozip/support-requests/18/</link><description>'custom' zip/unzip?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">miskox</dc:creator><pubDate>Tue, 20 Sep 2022 07:15:29 -0000</pubDate><guid>https://sourceforge.net/p/infozip/support-requests/18/</guid></item><item><title>Ed Gordon posted a comment on ticket #69</title><link>https://sourceforge.net/p/infozip/bugs/69/?limit=25#354c</link><description>I'll have to look, but basic zip encryption is a funny thing. The original authors made some assumptions on how to do it, which were accepted by others. I'll try to look at this in the next week and refresh myself on what's going on. I believe the answer is driven by what information is available when during the encryption process. Given how weak basic zip encryption is, it probably shouldn't be used much now, except in cases where cracking is not much of a concern. Zip 3.1e, whenever that is finalized,...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ed Gordon</dc:creator><pubDate>Tue, 02 Aug 2022 17:14:52 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/69/?limit=25#354c</guid></item><item><title>Paul Marquess created ticket #69</title><link>https://sourceforge.net/p/infozip/bugs/69/</link><description>Encryption enabled streaming</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul Marquess</dc:creator><pubDate>Tue, 02 Aug 2022 09:48:40 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/69/</guid></item><item><title>Ed Gordon posted a comment on ticket #61</title><link>https://sourceforge.net/p/infozip/bugs/61/?limit=25#2284</link><description>This looks the same as bug #68. As noted there, the --force option seems to be working, but the code that creates the Zip64 headers is not being told to do that. Adding this bug to the queue of Zip bugs to work. It should be a fairly quick fix, but no telling when we'll get Zip 3.1 out with it.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ed Gordon</dc:creator><pubDate>Mon, 01 Aug 2022 18:45:05 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/61/?limit=25#2284</guid></item><item><title>Ed Gordon posted a comment on ticket #68</title><link>https://sourceforge.net/p/infozip/bugs/68/?limit=25#c233</link><description>The analysis looks right. The --force option seems to be working correctly, but the code that generates the Zip64 headers is not detecting that the headers are needed. And it does seem the same issue as #61. I'll throw this on the queue of issues with Zip that need to be fixed. It should be a fairly quick fix, but no promises when Zip 3.1 will be released with it. Thanks for the feedback.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ed Gordon</dc:creator><pubDate>Mon, 01 Aug 2022 18:44:18 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/68/?limit=25#c233</guid></item><item><title>Paul Marquess created ticket #68</title><link>https://sourceforge.net/p/infozip/bugs/68/</link><description>Creating zip with Streamed Zip64 is missing central header records</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul Marquess</dc:creator><pubDate>Mon, 01 Aug 2022 14:56:04 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/68/</guid></item><item><title>Et7f3 posted a comment on ticket #31</title><link>https://sourceforge.net/p/infozip/patches/31/?limit=25#708b</link><description>The current codebase for 610b trigger those warnings: -Wformat-security -Wunused-const-variable -Wunused-variable -Wself-assign -Wformat here is a patch that fix some of those. You can find grep -r Info'(' | grep define to find other spot that trigger this warning. I wanted to fix with #define STRING "e" but I can't test on all OS so I let you test it.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Et7f3</dc:creator><pubDate>Tue, 26 Jul 2022 17:45:18 -0000</pubDate><guid>https://sourceforge.net/p/infozip/patches/31/?limit=25#708b</guid></item><item><title>Et7f3 created ticket #31</title><link>https://sourceforge.net/p/infozip/patches/31/</link><description>Fix macOS build</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Et7f3</dc:creator><pubDate>Tue, 26 Jul 2022 15:31:06 -0000</pubDate><guid>https://sourceforge.net/p/infozip/patches/31/</guid></item><item><title>Danilo Spinella posted a comment on ticket #65</title><link>https://sourceforge.net/p/infozip/bugs/65/?limit=25#7573/2a01</link><description>Hi! We at openSUSE also are experiencing similar errors when using FORTIFY_SOURCE=3. You can try by compiling zip using -DFORTIFY_SOURCE=3 and using the following command line: $ touch α.txt $ zip a.zip α.txt openSUSE bug for reference: https://bugzilla.suse.com/show_bug.cgi?id=1200712</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Danilo Spinella</dc:creator><pubDate>Tue, 21 Jun 2022 14:34:03 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/65/?limit=25#7573/2a01</guid></item><item><title>Takashi Yano posted a comment on ticket #30</title><link>https://sourceforge.net/p/infozip/patches/30/?limit=25#55f0</link><description>Sorry, the comment is broken with above patch...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Takashi Yano</dc:creator><pubDate>Fri, 17 Jun 2022 10:14:03 -0000</pubDate><guid>https://sourceforge.net/p/infozip/patches/30/?limit=25#55f0</guid></item><item><title>Takashi Yano created ticket #30</title><link>https://sourceforge.net/p/infozip/patches/30/</link><description>[patch] Stop to replace some special characters in file name for cygwin.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Takashi Yano</dc:creator><pubDate>Fri, 17 Jun 2022 10:12:21 -0000</pubDate><guid>https://sourceforge.net/p/infozip/patches/30/</guid></item><item><title>Steven Schweda modified ticket #67</title><link>https://sourceforge.net/p/infozip/bugs/67/</link><description>Failure to properly handle archives with backward slashes under Linux</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Steven Schweda</dc:creator><pubDate>Fri, 15 Apr 2022 11:20:20 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/67/</guid></item><item><title>Steven Schweda posted a comment on ticket #67</title><link>https://sourceforge.net/p/infozip/bugs/67/?limit=25#3d4a</link><description>https://midnight-commander.org/ticket/4238 It's an upstream bug [...] Not on our tributary. It might be helpful if someone explained the actual situation in that other forum.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Steven Schweda</dc:creator><pubDate>Sat, 09 Apr 2022 12:20:21 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/67/?limit=25#3d4a</guid></item><item><title>Steven Schweda modified a comment on ticket #67</title><link>https://sourceforge.net/p/infozip/bugs/67/?limit=25#2c87</link><description>I need to apologize. Ok. unzip under Fedora 35 unpacks both archives with zero issues I can believe that. So, there's a bug: files in archive directories cannot be extracted by mask. Or, it's not a bug in UnZip, but you didn't treat "\" as a special character? Try "\\" instead of "\"? Using your other (smaller) example archive: proa$ ln -s ScreenRuler-v.0.8.1-Portable.zip SR.zip proa$ unzip -l SR.zip 'ScreenRuler-v.0.8.1-Portable\README.html' Archive: SR.zip Length Date Time Name --------- ----------...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Steven Schweda</dc:creator><pubDate>Wed, 06 Apr 2022 07:39:14 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/67/?limit=25#2c87</guid></item><item><title>Steven Schweda posted a comment on ticket #67</title><link>https://sourceforge.net/p/infozip/bugs/67/?limit=25#2c87</link><description>I need to apologize. Ok. unzip under Fedora 35 unpacks both archives with zero issues I can believe that. So, there's a bug: files in archive directories cannot be extracted by mask. Or, it's not a bug in UnZip, but you didn't treat "\" as a special character? Try "\" instead of "\"? Using your other (smaller) example archive: proa$ ln -s ScreenRuler-v.0.8.1-Portable.zip SR.zip proa$ unzip -l SR.zip 'ScreenRuler-v.0.8.1-Portable\README.html' Archive: SR.zip Length Date Time Name --------- ----------...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Steven Schweda</dc:creator><pubDate>Tue, 05 Apr 2022 19:44:56 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/67/?limit=25#2c87</guid></item><item><title>Artem S. Tashkinov modified a comment on ticket #67</title><link>https://sourceforge.net/p/infozip/bugs/67/?limit=25#fe57</link><description>I need to apologize. unzip under Fedora 35 unpacks both archives with zero issues The issue is Midnight Commander which tries to parse unzip -l output and fails spectacularly: https://midnight-commander.org/ticket/4238 Still, I've identified a bug: $ unzip macintosh.js-win32-ia32-1.1.0.zip 'swiftshader\libEGL.dll' Archive: macintosh.js-win32-ia32-1.1.0.zip caution: filename not matched: swiftshader\libEGL.dll $ unzip macintosh.js-win32-ia32-1.1.0.zip 'swiftshader/libEGL.dll' Archive: macintosh.js-win32-ia32-1.1.0.zip...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Artem S. Tashkinov</dc:creator><pubDate>Tue, 05 Apr 2022 03:17:55 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/67/?limit=25#fe57</guid></item><item><title>Artem S. Tashkinov posted a comment on ticket #67</title><link>https://sourceforge.net/p/infozip/bugs/67/?limit=25#fe57</link><description>I need to apologize. unzip under Fedora 35 unpacks both archives with zero issues The issue is Midnight Commander which tries to parse unzip -l output and fails spectacularly: https://midnight-commander.org/ticket/4238 Still, I've identified a bug: $ unzip macintosh.js-win32-ia32-1.1.0.zip 'swiftshader\libEGL.dll' Archive: macintosh.js-win32-ia32-1.1.0.zip caution: filename not matched: swiftshader\libEGL.dll $ unzip macintosh.js-win32-ia32-1.1.0.zip 'swiftshader/libEGL.dll' Archive: macintosh.js-win32-ia32-1.1.0.zip...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Artem S. Tashkinov</dc:creator><pubDate>Tue, 05 Apr 2022 03:17:02 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/67/?limit=25#fe57</guid></item><item><title>Steven Schweda posted a comment on ticket #67</title><link>https://sourceforge.net/p/infozip/bugs/67/?limit=25#1302</link><description>The current behavior of UnZip (or Apple's Archive Utility app) makes some sense, [...] More than I had realized. I apologize. Initially, I was too lazy to do the extraction; I just looked at a listing ("unzip -l"), and saw the backslashes. "Trust no one," I always say. So, today, I actually did the work, and noticed that UnZip apparently already handles this situation, which my tired, old brain had forgotten. Around here, on a Mac, for example: proa$ mkdir SR proa$ cd SR proa$ unzip6 ../ScreenRuler-v.0.8.1-Portable.zip...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Steven Schweda</dc:creator><pubDate>Sun, 03 Apr 2022 19:47:56 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/67/?limit=25#1302</guid></item><item><title>Artem S. Tashkinov modified a comment on ticket #67</title><link>https://sourceforge.net/p/infozip/bugs/67/?limit=25#0c51/65b0</link><description>As always, a program version number would be helpful, but it probably doesn't matter much in this case. unzip-6.0-53.fc35.x86_64 : https://src.fedoraproject.org/rpms/unzip/tree/rawhide One possible solution would be to enhance UnZip to convert "\" to "/" in the (path) names of archive members In my 25 years of using UNIX OSes I've not seen a single filename containing back slashes. I'd just go ahead and convert \ in filenames to / automatically but I'm not a C programmer. You might also complain...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Artem S. Tashkinov</dc:creator><pubDate>Sun, 03 Apr 2022 13:14:35 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/67/?limit=25#0c51/65b0</guid></item><item><title>Artem S. Tashkinov posted a comment on ticket #67</title><link>https://sourceforge.net/p/infozip/bugs/67/?limit=25#0c51/65b0</link><description>As always, a program version number would be helpful, but it probably doesn't matter much in this case. unzip-6.0-53.fc35.x86_64 : https://src.fedoraproject.org/rpms/unzip/tree/rawhide One possible solution would be to enhance UnZip to convert "\" to "/" in the (path) names of archive members In my 25 years of using UNIX OSes I've not seen a single filename containing back slashes. I'd just go ahead and convert \ in filenames to / automatically but I'm not a C programmer. You might also complain...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Artem S. Tashkinov</dc:creator><pubDate>Sun, 03 Apr 2022 13:13:28 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/67/?limit=25#0c51/65b0</guid></item><item><title>Steven Schweda posted a comment on ticket #67</title><link>https://sourceforge.net/p/infozip/bugs/67/?limit=25#0c51</link><description>unzip [...] As always, a program version number would be helpful, but it probably doesn't matter much in this case. unzip -v [...] doesn't properly handle archives with backward slashes under Linux. I just ran into this problem in a Ford/Microsoft SYNC software update kit a few days ago. If you try to unpack any of them, you'll get funny results. That depends on your sense of humor. One could argue about what "properly" means in this case. Such archives do not conform to the zip archive standard,...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Steven Schweda</dc:creator><pubDate>Sat, 02 Apr 2022 05:55:21 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/67/?limit=25#0c51</guid></item><item><title>Artem S. Tashkinov created ticket #67</title><link>https://sourceforge.net/p/infozip/bugs/67/</link><description>Failure to properly handle archives with backward slashes under Linux</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Artem S. Tashkinov</dc:creator><pubDate>Sat, 02 Apr 2022 03:56:16 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/67/</guid></item><item><title>Bernhard M. Wiedemann posted a comment on ticket #25</title><link>https://sourceforge.net/p/infozip/patches/25/?limit=25#d914/35f4/bc42/d36a</link><description>There was a bug in the 1st scandir call param: "." vs n https://github.com/distropatches/zip/commit/5063c9ce12c58f2512c2d00080d863d14b5d31f7</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Bernhard M. Wiedemann</dc:creator><pubDate>Sun, 13 Feb 2022 09:41:10 -0000</pubDate><guid>https://sourceforge.net/p/infozip/patches/25/?limit=25#d914/35f4/bc42/d36a</guid></item><item><title>Steven Schweda posted a comment on ticket #60</title><link>https://sourceforge.net/p/infozip/bugs/60/?limit=25#272e</link><description>I see that Mark Adler has addressed the zip bomb issue [...] That code is incompatible with the LZMA and PPMd code in the current development code, and it seems to have trouble with bzip2, too. Adding this feature to UnZip (for all supported compression and encryption schemes) is the current task, but I haven't had much time to devote to it recently. Some progress is possible, however. I would like an official organization and repository by product too, to have a better development and contributions....</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Steven Schweda</dc:creator><pubDate>Tue, 28 Dec 2021 05:43:53 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/60/?limit=25#272e</guid></item><item><title>Neustradamus modified a comment on ticket #66</title><link>https://sourceforge.net/p/infozip/bugs/66/?limit=100#afbc</link><description>I would like an official organization and repository by product too, to have a better development and contributions. I think it is very important to do it quickly, we are in 2021, soon in 2022. Linked to: - https://sourceforge.net/p/infozip/feature-requests/8/ - https://sourceforge.net/p/infozip/bugs/60/ - https://sourceforge.net/p/infozip/bugs/66/ Note that Mark Adler has done a fork here: - https://github.com/madler/unzip</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Neustradamus</dc:creator><pubDate>Sun, 26 Dec 2021 19:58:42 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/66/?limit=100#afbc</guid></item><item><title>Neustradamus modified a comment on ticket #8</title><link>https://sourceforge.net/p/infozip/feature-requests/8/?limit=100#02c0</link><description>I would like an official organization and repository by product too, to have a better development and contributions. I think it is very important to do it quickly, we are in 2021, soon in 2022. Linked to: - https://sourceforge.net/p/infozip/feature-requests/8/ - https://sourceforge.net/p/infozip/bugs/60/ - https://sourceforge.net/p/infozip/bugs/66/ Note that Mark Adler has done a fork here: - https://github.com/madler/unzip</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Neustradamus</dc:creator><pubDate>Sun, 26 Dec 2021 19:58:30 -0000</pubDate><guid>https://sourceforge.net/p/infozip/feature-requests/8/?limit=100#02c0</guid></item><item><title>Neustradamus posted a comment on ticket #60</title><link>https://sourceforge.net/p/infozip/bugs/60/?limit=100#9aee</link><description>I would like an official organization and repository by product too, to have a better development and contributions. I think it is very important to do it quickly, we are in 2021, soon in 2022. Linked to: - https://sourceforge.net/p/infozip/feature-requests/8/ - https://sourceforge.net/p/infozip/bugs/60/ - https://sourceforge.net/p/infozip/bugs/66/ Note that Mark Adler has done a fork here: - https://github.com/madler/unzip</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Neustradamus</dc:creator><pubDate>Sun, 26 Dec 2021 19:58:23 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/60/?limit=100#9aee</guid></item><item><title>Neustradamus posted a comment on ticket #66</title><link>https://sourceforge.net/p/infozip/bugs/66/?limit=100#afbc</link><description>I would like an official repo too, to have a better development and contributions. I think it is very important to do it quickly, we are in 2021, soon in 2022. Linked to: - https://sourceforge.net/p/infozip/feature-requests/8/ - https://sourceforge.net/p/infozip/bugs/60/ - https://sourceforge.net/p/infozip/bugs/66/ -</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Neustradamus</dc:creator><pubDate>Sun, 26 Dec 2021 19:55:51 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/66/?limit=100#afbc</guid></item><item><title>Neustradamus posted a comment on ticket #8</title><link>https://sourceforge.net/p/infozip/feature-requests/8/?limit=100#02c0</link><description>I would like an official repo too, to have a better development and contributions. I think it is very important to do it quickly, we are in 2021, soon in 2022. Linked to: - https://sourceforge.net/p/infozip/feature-requests/8/ - https://sourceforge.net/p/infozip/bugs/60/ - https://sourceforge.net/p/infozip/bugs/66/ -</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Neustradamus</dc:creator><pubDate>Sun, 26 Dec 2021 19:55:31 -0000</pubDate><guid>https://sourceforge.net/p/infozip/feature-requests/8/?limit=100#02c0</guid></item><item><title>Steven Schweda posted a comment on ticket #66</title><link>https://sourceforge.net/p/infozip/bugs/66/?limit=25#c563</link><description>Is it anywhere git repo with curent unzip code? No. Currently, Zip and UnZip source code is maintained privately by the maintainers. If not is it possible to create such repo on github or gitlab? (SF git frontend sucks) It may be possible, but we haven't decided to do it. What do you want to do? If you'd like, I could provide links to the latest available (2018) unreleased UnZip development code.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Steven Schweda</dc:creator><pubDate>Sat, 18 Dec 2021 22:40:19 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/66/?limit=25#c563</guid></item><item><title>Tomasz K&amp;#322;oczko created ticket #66</title><link>https://sourceforge.net/p/infozip/bugs/66/</link><description>unzip project git repo?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tomasz K&amp;#322;oczko</dc:creator><pubDate>Sat, 18 Dec 2021 21:43:47 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/66/</guid></item><item><title>Steven Schweda modified a comment on ticket #17</title><link>https://sourceforge.net/p/infozip/support-requests/17/?limit=25#1ae3</link><description>[...] I downloaded the latest version of Zip again,that is Zip 3.0(dated 07-2008).But there seems to be differences in a few header files [...] "differences" between which kit and which other kit, exactly? Zip 3.0 should be Zip 3.0. Various Zip 3.0XXX beta kits were produced (some public, some private), but they should all have unique identification. Similarly, various Zip 3.1XXX beta kits have been produced (some public, some private), but they, too, should all have unique identification. If you've...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Steven Schweda</dc:creator><pubDate>Wed, 07 Jul 2021 21:35:40 -0000</pubDate><guid>https://sourceforge.net/p/infozip/support-requests/17/?limit=25#1ae3</guid></item><item><title>Steven Schweda posted a comment on ticket #17</title><link>https://sourceforge.net/p/infozip/support-requests/17/?limit=25#1ae3</link><description>&gt; [...] I downloaded the latest version of Zip again,that is Zip &gt; 3.0(dated 07-2008).But there seems to be differences in a few header &gt; files [...] "differences" between what and what, exactly? Zip 3.0 should be Zip 3.0. Various Zip 3.0XXX beta kits were produced (some public, some private), but they should all have unique identification. Similarly, various Zip 3.1XXX beta kits have been produced (some public, some private), but they, too, should all have unique identification. If you've linked...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Steven Schweda</dc:creator><pubDate>Wed, 07 Jul 2021 21:31:23 -0000</pubDate><guid>https://sourceforge.net/p/infozip/support-requests/17/?limit=25#1ae3</guid></item><item><title>Ashrita created ticket #17</title><link>https://sourceforge.net/p/infozip/support-requests/17/</link><description>Differences in header files</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ashrita</dc:creator><pubDate>Wed, 07 Jul 2021 17:26:34 -0000</pubDate><guid>https://sourceforge.net/p/infozip/support-requests/17/</guid></item><item><title>Tomasz K&amp;#322;oczko created ticket #8</title><link>https://sourceforge.net/p/infozip/feature-requests/8/</link><description>GIT repo</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tomasz K&amp;#322;oczko</dc:creator><pubDate>Mon, 03 May 2021 08:02:27 -0000</pubDate><guid>https://sourceforge.net/p/infozip/feature-requests/8/</guid></item><item><title>Tomáš Beránek modified a comment on ticket #64</title><link>https://sourceforge.net/p/infozip/bugs/64/?limit=25#1526</link><description>The analyzed package was zip-3.0-27.fc33 (default version on Fedora 33 from the official repository https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-33&amp;arch=x86_64). I wasn't able to find version zip31d on this site, only zip31c which seems to be the latest modified. I have checked the issues against this version and they are still present, but line numbers are a bit different. Updated line numbers: 1) unix/unix.c:343: error: Null Dereference When i was looking at the issue again, i noticed...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tomáš Beránek</dc:creator><pubDate>Tue, 13 Apr 2021 04:58:28 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/64/?limit=25#1526</guid></item><item><title>Tomáš Beránek modified a comment on ticket #64</title><link>https://sourceforge.net/p/infozip/bugs/64/?limit=25#1526</link><description>The analyzed package was zip-3.0-27.fc33 (default version on Fedora 33 from the official repository https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-33&amp;arch=x86_64). I wasn't able to find version zip31d on this site, only zip31c which seems to be the latest modified. I have checked the issues against this version and they are still present, but line numbers are a bit different. Updated line numbers: 1) unix/unix.c:343: error: Null Dereference When i was looking at the issue again, i noticed...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tomáš Beránek</dc:creator><pubDate>Tue, 13 Apr 2021 04:57:25 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/64/?limit=25#1526</guid></item><item><title>Tomáš Beránek posted a comment on ticket #64</title><link>https://sourceforge.net/p/infozip/bugs/64/?limit=25#1526</link><description>The analyzed package was zip-3.0-27.fc33 (default version on Fedora 33). I wasn't able to find version zip31d on this site, only zip31c which seems to be the latest modified. I have checked the issues against this version and they are still present, but line numbers are a bit different. Updated line numbers: 1) unix/unix.c:343: error: Null Dereference When i was looking at the issue again, i noticed that for x == "//" the NULL dereference won't happen, but for x == "//host" or "//host/share" will....</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tomáš Beránek</dc:creator><pubDate>Tue, 13 Apr 2021 04:40:43 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/64/?limit=25#1526</guid></item><item><title>Ed Gordon modified a comment on ticket #65</title><link>https://sourceforge.net/p/infozip/bugs/65/?limit=25#7573</link><description>We'll take a look at the zip-bug page. What version of Zip and what OS was the buffer overflow on? If you downloaded Zip, where did you get it? What command line did you use to create this? What can you tell us about the file being recovered (big, small, type)? If you can provide an example, without any sensitive data and small, that recreates the issue that would be very helpful. It's possible the latest beta fixed this issue already.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ed Gordon</dc:creator><pubDate>Thu, 08 Apr 2021 16:46:20 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/65/?limit=25#7573</guid></item><item><title>Ed Gordon posted a comment on ticket #65</title><link>https://sourceforge.net/p/infozip/bugs/65/?limit=25#7573</link><description>We'll take a look at that.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ed Gordon</dc:creator><pubDate>Thu, 08 Apr 2021 16:40:46 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/65/?limit=25#7573</guid></item><item><title>Ed Gordon posted a comment on ticket #64</title><link>https://sourceforge.net/p/infozip/bugs/64/?limit=25#0554</link><description>Sorry for the delay getting back to you. Where did you download this copy of Zip? Just want to confirm we are looking at the same package. Note that end providers, like Fedora, tend to edit our base packages before including them in their distributions. That said, we've made considerable modifications to Zip. Beta version Zip 3.1d should be on this site. Version Zip 3.1e hopefully should be hopefully posting in a month or so and should be close to being released as Zip 3.1. I'll check the latest...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ed Gordon</dc:creator><pubDate>Thu, 08 Apr 2021 16:34:42 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/64/?limit=25#0554</guid></item><item><title>David Durgee posted a comment on ticket #65</title><link>https://sourceforge.net/p/infozip/bugs/65/?limit=25#baf1</link><description>Another point for you, I attempted to report this bug by the link http://www.info-zip.org/zip-bug.html but it results in an error about an empty README or some such.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">David Durgee</dc:creator><pubDate>Wed, 07 Apr 2021 15:46:47 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/65/?limit=25#baf1</guid></item><item><title>David Durgee created ticket #65</title><link>https://sourceforge.net/p/infozip/bugs/65/</link><description>buffer overflow detected during attempted recovery of zip</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">David Durgee</dc:creator><pubDate>Wed, 07 Apr 2021 15:42:32 -0000</pubDate><guid>https://sourceforge.net/p/infozip/bugs/65/</guid></item></channel></rss>