From: Reto Brunner <brunnre8@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Re: PostUp/PreUp/PostDown/PreDown Dangerous?
Date: Sat, 23 Jun 2018 21:16:54 +0200 [thread overview]
Message-ID: <20180623191654.4k3bd2y5p3dplkty@ghostArch.localdomain> (raw)
In-Reply-To: <c80282cc-5c43-e2fc-3656-efeca01c15b6@ironicdesign.com>
On Fri, Jun 22, 2018 at 09:07:43AM -0500, Andy Dorman wrote:
> So, while it should be obvious, it wouldn't hurt to add a short warning (in
> bold) to the wg-quick man page that lets these "amateur" users know of the
> potential danger.
The issue being that people do not tend to read the man pages.
I don't disagree that this might be useful for some, but don't get your
hopes up too much...
The type of user who actually needs this warning tends to not want to
put in any effort whatsoever in understanding how stuff works, they just want the end result.
This is at least my experience from several Linux irc channels, where
half the questions could be answered by `man $program_I_have_issues_with`
next prev parent reply other threads:[~2018-06-23 19:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 1:34 PostUp/PreUp/PostDown/PreDown Dangerous? Jason A. Donenfeld
2018-06-22 1:35 ` Jason A. Donenfeld
2018-06-22 1:41 ` Jason A. Donenfeld
2018-06-22 1:55 ` logcabin
2018-06-22 1:56 ` Antonio Quartulli
2018-06-22 10:46 ` Jordan Glover
2018-06-22 10:53 ` Antonio Quartulli
2018-06-22 13:08 ` Jacob Baines
2018-06-22 14:47 ` Andy Dorman
2018-06-22 15:14 ` Matthias Urlichs
2018-06-22 17:11 ` Jason A. Donenfeld
2018-06-22 4:01 ` Matthias Urlichs
2018-06-22 5:44 ` Reto Brunner
2018-06-22 14:07 ` Andy Dorman
2018-06-23 19:16 ` Reto Brunner [this message]
2018-06-22 19:26 ` Lonnie Abelbeck
2018-06-22 22:13 ` Jordan Glover
2018-06-23 2:36 ` Antonio Quartulli
2018-06-23 7:02 ` Dario Bosch
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=20180623191654.4k3bd2y5p3dplkty@ghostArch.localdomain \
--to=brunnre8@gmail.com \
--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).