From: John Kehayias via Guix-patches via <guix-patches@gnu.org>
To: Vagrant Cascadian <vagrant@reproducible-builds.org>
Cc: 69007@debbugs.gnu.org
Subject: [bug#69007] diffoscope: Update to 256. [security fixes]
Date: Fri, 09 Feb 2024 21:41:27 +0000 [thread overview]
Message-ID: <87mss98ge4.fsf@protonmail.com> (raw)
In-Reply-To: <87r0hl2us9.fsf@wireframe>
Hi vagrant!
On Fri, Feb 09, 2024 at 01:27 PM, Vagrant Cascadian wrote:
> The attached patch updates diffoscope to 256, which contains a security
> fix for directory traversals when using gpg.
>
> Both diffoscope and it's dependent, reprotest, still build fine!
>
Great, thank you! (following up here for posterity; discussed via IRC)
> I am not sure what the expedited process for security updates are, but
> if there is anything I can do, please let me know!
>
As we discussed, we should formalize some CC-ing of the security list,
or a separate security team for reviewing patches (for public flaws,
rather than reporting them). And making sure "[security fixes]" is
noted, as you did here, for easy sorting.
> live well,
> vagrant
>
> From 9dcababcf0e94ddab30de91054e04400b263879c Mon Sep 17 00:00:00 2001
> From: Vagrant Cascadian <vagrant@debian.org>
> Date: Fri, 9 Feb 2024 12:58:57 -0800
> Subject: [PATCH] gnu: diffoscope: Update to 256. [security fixes]
>
In any event, patch looks good and as a leaf with a pretty trivial
patch, I think you would be clear to push directly to begin with. There
was some discussion a while back at what is "trivial," but a version
update with 1 dependent is about as easy as it gets. Perhaps another
thing to make sure we are on the same page about but I doubt anyone
would complain if you had pushed this directly.
We could also let QA build, since it is back up, but again, very minor
concern here if something were to break.
Anyway, please do push! I might put "[security fixes]" before the period
in the commit message to match previous ones, but that is very minor.
Thanks again!
John
> Fixes: https://salsa.debian.org/reproducible-builds/diffoscope/-/issues/361
>
> * gnu/packages/diffoscope.scm (diffoscope): Update to 256.
> ---
> gnu/packages/diffoscope.scm | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/gnu/packages/diffoscope.scm b/gnu/packages/diffoscope.scm
> index 626ac00425..f4d271f690 100644
> --- a/gnu/packages/diffoscope.scm
> +++ b/gnu/packages/diffoscope.scm
> @@ -74,7 +74,7 @@ (define-module (gnu packages diffoscope)
> (define-public diffoscope
> (package
> (name "diffoscope")
> - (version "255")
> + (version "256")
> (source
> (origin
> (method git-fetch)
> @@ -83,7 +83,7 @@ (define-public diffoscope
> (commit version)))
> (file-name (git-file-name name version))
> (sha256
> - (base32 "07mkmwp3ni2dh5w5q2vxkc588l5dabcly3jrd8ic62318si7d400"))))
> + (base32 "1sdg314a3hp2kv492130p8w7j8mlhymij7h2rndm4q7gqrshp6jf"))))
> (build-system python-build-system)
> (arguments
> (list
>
> base-commit: 513755d64debb44096f21e323a5b89a7a597d2ca
next prev parent reply other threads:[~2024-02-09 21:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 21:27 [bug#69007] diffoscope: Update to 256. [security fixes] Vagrant Cascadian
2024-02-09 21:41 ` John Kehayias via Guix-patches via [this message]
2024-02-09 22:18 ` bug#69007: " Vagrant Cascadian
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=87mss98ge4.fsf@protonmail.com \
--to=guix-patches@gnu.org \
--cc=69007@debbugs.gnu.org \
--cc=john.kehayias@protonmail.com \
--cc=vagrant@reproducible-builds.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.
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).