From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Reuben Martin <reuben.m.work@gmail.com>,
WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: wireguard dkms systemd
Date: Sun, 04 Nov 2018 10:24:56 +0700 [thread overview]
Message-ID: <87o9b5frsn.fsf@fifthhorseman.net> (raw)
In-Reply-To: <CALJ2VGaq8AasV99YApW5UWEKK0B-r+uafT7nEjbKARfwADab+A@mail.gmail.com>
On Fri 2018-11-02 18:27:55 -0500, Reuben Martin wrote:
> All this discussion about service management kinda misses the
> point. You're swapping out a kernel module. There will always be
> risk. Changing service management procedures won't mitigate that. If
> you do not have a means to connect outside of the VPN connection, and
> the module (or service) fail, you're SOL.
I think you're saying that such a migration is complicated,
idiosyncratic, and might fail -- so we should automate it and let the
admin pick up the pieces if it breaks.
I think i agree that it's complicated, idiosyncratic, and might fail --
by my conclusion is that we *shouldn't* automate it on behalf of the
local admin, but rather let them plan their own migration. *shrug*
Again, if you have a suggestion for how to reduce the risk, i'm all
ears, but i'm not about to encourage automated breakage in the package
management.
--dkg
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2018-11-04 3:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 20:59 Lucian Cristian
2018-10-20 21:07 ` Robert-André Mauchin
2018-10-21 12:12 ` Jordan Glover
2018-10-21 15:49 ` Lucian Cristian
2018-11-02 13:52 ` Daniel Kahn Gillmor
2018-11-02 23:27 ` Reuben Martin
2018-11-04 3:24 ` Daniel Kahn Gillmor [this message]
2018-11-04 15:35 ` Jason A. Donenfeld
2018-11-05 6:28 ` Daniel Kahn Gillmor
2018-11-05 11:27 ` Fabian Grünbichler
2018-11-06 7:16 ` Daniel Kahn Gillmor
2018-11-06 13:04 ` Fabian Grünbichler
2018-11-07 2:29 ` Daniel Kahn Gillmor
2018-11-05 15:51 ` Jason A. Donenfeld
2018-11-03 11:54 ` Matthias Urlichs
2018-11-04 3:22 ` Daniel Kahn Gillmor
2018-10-21 13:01 ` Jonathon Fernyhough
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=87o9b5frsn.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=reuben.m.work@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).