All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Claire Elaina <git@claire.sharkgirl.ing>
Cc: wireguard@lists.zx2c4.com, adam.irr@outlook.com
Subject: Re: [PATCH wireguard-tools] wg-quick: android: add support for {Pre,  Post}{Up, Down} hooks
Date: Sun, 25 May 2025 14:45:29 +0200	[thread overview]
Message-ID: <aDMQ6eE_aIUTV4dB@zx2c4.com> (raw)
In-Reply-To: <20250525080457.998659-1-git@claire.sharkgirl.ing>

On Sun, May 25, 2025 at 06:04:57PM +1000, Claire Elaina wrote:
> +static void execute_hooks(const struct str_list *hooks)
> +{
> +	for (size_t i = 0; i < hooks->len; ++i)
> +		cmd("%s", hooks->items[i]);
> +}

This was also posted here, so copying Adam:
https://lore.kernel.org/wireguard/DM6PR13MB24579CD788EF28E019933C0A92609@DM6PR13MB2457.namprd13.prod.outlook.com/
https://github.com/WireGuard/wireguard-android/pull/23

This feature is appealing, but I've always held off on it because I'm
afraid of the malware potential on client platforms where people are
pretty looseygoosey with loading in random config files. Even on
Windows, it only got added behind a hidden registry setting. If we added
it here, maybe it'd need to be quite gated too. But then how do we
handle cases where a config had it but it was disabled and then it gets
enabled and it's there by surprise? Maybe strip it out on import if it's
disabled? What about the transition from root to non-root and back?
Anyway, many questions.

Wondering, what commands do you want to run?

Jason

  reply	other threads:[~2025-05-25 12:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-25  8:04 [PATCH wireguard-tools] wg-quick: android: add support for {Pre, Post}{Up, Down} hooks Claire Elaina
2025-05-25 12:45 ` Jason A. Donenfeld [this message]
2025-05-25 22:45   ` Claire

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=aDMQ6eE_aIUTV4dB@zx2c4.com \
    --to=jason@zx2c4.com \
    --cc=adam.irr@outlook.com \
    --cc=git@claire.sharkgirl.ing \
    --cc=wireguard@lists.zx2c4.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.