From: ifreund <ifreund@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] vips: update to 8.11.0.
Date: Mon, 28 Jun 2021 16:44:32 +0200 [thread overview]
Message-ID: <20210628144432.xN0G-01lWyRDKV9nNNbx7_EOBPodsvZNsRBIP-RhvVI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31685@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 720 bytes --]
New review comment by ifreund on void-packages repository
https://github.com/void-linux/void-packages/pull/31685#discussion_r659852088
Comment:
The `libMagick` dependency is not included in the vips package we currently ship because one of the major reasons to use vips over ImageMagick is that it is much smaller/cleaner/more auditable and more suited to use with untrusted image inputs.
From the vips readme's [ImageMagick section](https://github.com/libvips/libvips#imagemagick-or-optionally-graphicsmagick):
> If you are going to be using libvips with untrusted images, perhaps in a web server, for example, you should consider the security implications of enabling a package with such a large attack surface.
next prev parent reply other threads:[~2021-06-28 14:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-27 18:32 [PR PATCH] " ifreund
2021-06-27 18:33 ` [PR PATCH] [Updated] " ifreund
2021-06-28 14:18 ` [PR REVIEW] " ericonr
2021-06-28 14:18 ` ericonr
2021-06-28 14:18 ` ericonr
2021-06-28 14:39 ` [PR PATCH] [Updated] " ifreund
2021-06-28 14:44 ` [PR REVIEW] " ifreund
2021-06-28 14:44 ` ifreund [this message]
2021-06-28 14:46 ` ifreund
2021-06-28 15:08 ` ericonr
2021-06-28 15:14 ` [PR PATCH] [Updated] " ifreund
2021-06-28 15:14 ` [PR REVIEW] " ifreund
2021-06-28 16:23 ` [PR PATCH] [Merged]: " ericonr
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210628144432.xN0G-01lWyRDKV9nNNbx7_EOBPodsvZNsRBIP-RhvVI@z \
--to=ifreund@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
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 NNTP newsgroup(s).