unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: John Kehayias <john.kehayias@protonmail.com>
Cc: 70114@debbugs.gnu.org, 70113-done@debbugs.gnu.org
Subject: bug#70113: [PATCH 1/1] gnu: libarchive: Fix a potential security issue.
Date: Wed, 3 Apr 2024 18:08:12 -0400	[thread overview]
Message-ID: <Zg3TTEwIZkIObXc0@jasmine.lan> (raw)
In-Reply-To: <87il10wipx.fsf@protonmail.com>

[-- Attachment #1: Type: text/plain, Size: 509 bytes --]

On Tue, Apr 02, 2024 at 03:23:44AM +0000, John Kehayias wrote:
> Overall changes look good, but I have not had a chance to try it locally
> (building or dependents).

I successfully tested with the file-roller package, which depends
directly on libarchive and no other related packages. I think it's a
reasonable basic test case.

I agree it's a good idea to look into a more comprehensive update to
libarchive, but I just wanted to get this patch in ASAP.

Pushed as 629614c7a3f9283306939402f1ff46914f327c21

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2024-04-03 22:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-31 20:44 [bug#70114] [PATCH 0/1] Xz backdoor / JiaT75 cleanup for libarchive Leo Famulari
2024-03-31 20:44 ` [bug#70113] [PATCH 1/1] gnu: libarchive: Fix a potential security issue Leo Famulari
2024-03-31 20:51   ` [bug#70113] SECURITY: Xz backdoor / JiaT75 cleanup for libarchive Leo Famulari
2024-04-02  3:23 ` [bug#70114] [bug#70113] [PATCH 1/1] gnu: libarchive: Fix a potential security issue John Kehayias via Guix-patches via
2024-04-02 13:24   ` Efraim Flashner
2024-04-02 13:45   ` pelzflorian (Florian Pelz)
2024-04-04  2:38     ` John Kehayias via Guix-patches via
2024-04-03 22:08   ` Leo Famulari [this message]

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=Zg3TTEwIZkIObXc0@jasmine.lan \
    --to=leo@famulari.name \
    --cc=70113-done@debbugs.gnu.org \
    --cc=70114@debbugs.gnu.org \
    --cc=john.kehayias@protonmail.com \
    /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).