unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "Noé Lopez" <noe@xn--no-cja.eu>
Cc: 73842@debbugs.gnu.org
Subject: [bug#73842] [PATCH v5 2/3] pack: Add support for AppImage pack format.
Date: Wed, 20 Nov 2024 13:05:15 +0100	[thread overview]
Message-ID: <87ed36xg90.fsf@gnu.org> (raw)
In-Reply-To: <87ttc5q1b3.fsf@xn--no-cja.eu> ("Noé Lopez"'s message of "Sun, 17 Nov 2024 17:20:48 +0100")

Hi,

(+Cc: issue.)

Noé Lopez <noe@noé.eu> skribis:

> This is an expected error from the AppImage runtime, as said in the
> output the runtime depends on FUSE 3 to mount the AppImage.
>
> The AppImage can still be ran using --appimage-extract-and-run, which I
> believe we noted in the documentation:
>
>>The runtime used by AppImages makes use of libfuse to mount the image
>>quickly.  If libfuse is not available, the AppImage can still be started
>>using the @option{--appimage-extract-and-run} flag.

Oh right.  Perhaps we can tweak it to explicitly mention that
‘fusermount3’ must be in $PATH (as opposed to referring to “libfuse”).
WDYT?

(If you prefer I can make this change and push the whole thing; it’s
just a fine point.)

> As for things that can be done from our side, we could change runtime to
> one that uses other technologies just like supported by “-RR”.

Yup.  The two techniques are definitely close to one another!

> I’m pretty sure a process attached with ptrace can’t exec SUID programs,
> for security reasons (ptrace allows you to change the code of the
> attached program so its a privilege escalation).

Yes, that makes sense.

Thank you!

Ludo’.




      parent reply	other threads:[~2024-11-20 12:07 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87ttc5q1b3.fsf@xn--no-cja.eu>
2024-10-16 21:51 ` [bug#73842] [PATCH] pack: Add support for AppImage pack format Noé Lopez
2024-10-18 12:20   ` Ludovic Courtès
2024-10-18 12:22   ` Ludovic Courtès
2024-10-18 20:34   ` Ludovic Courtès
2024-10-26 17:28   ` [bug#73842] [PATCH v2 0/3] " Noé Lopez
2024-10-26 17:28     ` [bug#73842] [PATCH v2 1/3] gnu: appimage: New packages for the appimage runtime Noé Lopez
2024-11-01 13:24       ` Maxim Cournoyer
2024-10-26 17:28     ` [bug#73842] [PATCH v2 2/3] pack: Add support for AppImage pack format Noé Lopez
2024-11-01 13:19       ` Maxim Cournoyer
2024-11-01 15:22         ` Noé Lopez via Guix-patches via
2024-10-26 17:28     ` [bug#73842] [PATCH v2 3/3] news: Add entry for guix pack’s AppImage format Noé Lopez
2024-10-27 13:38       ` pelzflorian (Florian Pelz)
2024-11-01 13:27       ` Maxim Cournoyer
2024-11-03 22:37   ` [bug#73842] [PATCH v4 0/3] pack: Add support for AppImage pack format Noé Lopez via Guix-patches via
2024-11-03 22:37     ` [bug#73842] [PATCH v4 1/3] gnu: appimage: New packages for the appimage runtime Noé Lopez via Guix-patches via
2024-11-05 14:22       ` Ludovic Courtès
2024-11-03 22:37     ` [bug#73842] [PATCH v4 2/3] pack: Add support for AppImage pack format Noé Lopez via Guix-patches via
2024-11-05 14:27       ` Ludovic Courtès
2024-11-03 22:37     ` [bug#73842] [PATCH v4 3/3] news: Add entry for guix pack’s AppImage format Noé Lopez via Guix-patches via
2024-11-05 14:28       ` Ludovic Courtès
2024-11-07 16:50   ` [bug#73842] [PATCH v5 1/3] gnu: appimage: New packages for the appimage runtime Noé Lopez via Guix-patches via
2024-11-07 16:50     ` [bug#73842] [PATCH v5 2/3] pack: Add support for AppImage pack format Noé Lopez via Guix-patches via
2024-11-15 17:02       ` Ludovic Courtès
2024-11-07 16:50     ` [bug#73842] [PATCH v5 3/3] news: Add entry for guix pack’s AppImage format Noé Lopez via Guix-patches via
2024-11-17 16:25   ` [bug#73842] [Noé Lopez] Re: [bug#73842] [PATCH v5 2/3] pack: Add support for AppImage pack format Noé Lopez via Guix-patches via
2024-11-20 12:05 ` Ludovic Courtès [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=87ed36xg90.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=73842@debbugs.gnu.org \
    --cc=noe@xn--no-cja.eu \
    /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).