From: Jordan Glover <Golden_Miller83@protonmail.ch>
To: "Jörg Thalheim" <joerg@higgsboson.tk>
Cc: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Re: [PATCH] treewide: more portable bash shebangs
Date: Wed, 17 Jul 2019 18:52:50 +0000 [thread overview]
Message-ID: <XHxn90sHSAhU8FiiH8HlaKCedl2W9YOY4Qzv0bfjAydxpP_K80LpTD-DNGmCWG4h6krilLjhoryjWE2c-uwCHjvhQPGIwnrg0UkZUbZxDGM=@protonmail.ch> (raw)
In-Reply-To: <55df869d-87e2-6d55-6e70-8b110cad2086@higgsboson.tk>
On Wednesday, July 17, 2019 6:39 PM, Jörg Thalheim <joerg@higgsboson.tk> wrote:
>
> It does not make anything worse. Your threat model is unreasonable and out of scope
> of what the scripts are intended to guarantee.
> There are tones of other environment variables like LD_PRELOAD or LD_LIBRARY_PATH
And how exactly you get into position to decide what
scope is reasonable for wireguard scripts?
Same as you I can clam that your use-case is out of scope and instead
of forcing everyone else to patch-out your changes you can go back to
patching the code by yourself in a way you wish and with accordance to
threat model you may or not have. Good luck.
Jordan
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2019-07-17 18:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 12:21 [PATCH] treewide: more portable bash shebangs Jörg Thalheim
2019-07-16 17:32 ` Jordan Glover
2019-07-16 20:07 ` Janne Johansson
2019-07-16 22:08 ` Jörg Thalheim
2019-07-17 17:32 ` Jordan Glover
2019-07-17 18:39 ` Jörg Thalheim
2019-07-17 18:52 ` Jordan Glover [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='XHxn90sHSAhU8FiiH8HlaKCedl2W9YOY4Qzv0bfjAydxpP_K80LpTD-DNGmCWG4h6krilLjhoryjWE2c-uwCHjvhQPGIwnrg0UkZUbZxDGM=@protonmail.ch' \
--to=golden_miller83@protonmail.ch \
--cc=joerg@higgsboson.tk \
--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 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 NNTP newsgroup(s).