From: nee <nee@cock.li>
To: Adonay Felipe Nogueira <adfeno@hyperbola.info>
Cc: 28602@debbugs.gnu.org
Subject: bug#28602: Unpack fails with no error message when using a .zip source
Date: Mon, 9 Oct 2017 23:05:02 +0200 [thread overview]
Message-ID: <1771470d-8b9a-a516-7da2-6532432955a4@cock.li> (raw)
In-Reply-To: <87wp4abwwm.fsf@hyperbola.info>
Am 04.10.2017 um 20:17 schrieb Adonay Felipe Nogueira:
> Does the .zip file have a a single directory on the root?
>
> If not, then we can call it a zipbomb/tarbomb. These bombs are bad
> because they can replace things without notice, and can be very
> difficult to track what was added. Last time I checked Guix expects only
> a single directory in the root of the file --- this might have changed,
> but I didn't test it since one year ago.
Hello, this is a different problem. Tarbombs are still a problem, but
unrelated to this.
The gnu-build-system does not have unzip by default. If a package's
source comes in a zip the package must have unzip as native-input. If it
isn't the (system* "unzip" source) call in the unpack function will fail
because there is no unzip executable.
Happy hacking!
next prev parent reply other threads:[~2017-10-09 21:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 20:10 bug#28602: Unpack fails with no error message when using a .zip source nee
2017-10-04 18:17 ` Adonay Felipe Nogueira
2017-10-09 21:05 ` nee [this message]
2017-10-09 21:00 ` bug#28602: [PATCH] guix: gnu-build-system: warn about missing unzip input unzip nee
2021-07-05 11:46 ` bug#28602: Unpack fails with no error message when using a .zip source zimoun
2021-11-26 1:49 ` bug#28602: [core-updates] " zimoun
2022-01-04 22:55 ` bug#28602: " zimoun
2022-03-23 10:37 ` zimoun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1771470d-8b9a-a516-7da2-6532432955a4@cock.li \
--to=nee@cock.li \
--cc=28602@debbugs.gnu.org \
--cc=adfeno@hyperbola.info \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).