From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-libs/tiff/files/
Date: Tue, 7 Feb 2023 04:30:13 +0000 (UTC) [thread overview]
Message-ID: <1675744191.847c95bdb5624d743c7e99bf10b1749580ace225.sam@gentoo> (raw)
commit: 847c95bdb5624d743c7e99bf10b1749580ace225
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Feb 7 04:04:56 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Feb 7 04:29:51 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=847c95bd
media-libs/tiff: scrub patch, add upstream refs
Signed-off-by: Sam James <sam <AT> gentoo.org>
media-libs/tiff/files/tiff-4.5.0-CVE-2022-48281.patch | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/media-libs/tiff/files/tiff-4.5.0-CVE-2022-48281.patch b/media-libs/tiff/files/tiff-4.5.0-CVE-2022-48281.patch
index 070f642da454..e38d17df9cc2 100644
--- a/media-libs/tiff/files/tiff-4.5.0-CVE-2022-48281.patch
+++ b/media-libs/tiff/files/tiff-4.5.0-CVE-2022-48281.patch
@@ -1,7 +1,7 @@
-Index: tiff-4.5.0/tools/tiffcrop.c
-===================================================================
---- tiff-4.5.0.orig/tools/tiffcrop.c
-+++ tiff-4.5.0/tools/tiffcrop.c
+https://gitlab.com/libtiff/libtiff/-/issues/488
+https://bugs.gentoo.org/891839
+--- a/tools/tiffcrop.c
++++ b/tools/tiffcrop.c
@@ -8591,7 +8591,7 @@ static int processCropSelections(struct
cropsize + NUM_BUFF_OVERSIZE_BYTES);
else
next reply other threads:[~2023-02-07 4:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 4:30 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-20 1:29 [gentoo-commits] repo/gentoo:master commit in: media-libs/tiff/files/ Aaron Bauman
2019-03-27 23:56 Patrice Clement
2018-06-13 21:18 Aaron Bauman
2016-12-29 13:14 David Seifert
2016-08-07 21:54 Lars Wendler
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=1675744191.847c95bdb5624d743c7e99bf10b1749580ace225.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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