From: Reuben Martin <reuben.m.work@gmail.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: wireguard dkms systemd
Date: Fri, 2 Nov 2018 18:27:55 -0500 [thread overview]
Message-ID: <CALJ2VGaq8AasV99YApW5UWEKK0B-r+uafT7nEjbKARfwADab+A@mail.gmail.com> (raw)
In-Reply-To: <87pnvnmvsc.fsf@fifthhorseman.net>
[-- Attachment #1.1: Type: text/plain, Size: 757 bytes --]
On Fri, Nov 2, 2018, 6:06 PM Daniel Kahn Gillmor <dkg@fifthhorseman.net
wrote:
> On Sun 2018-10-21 18:49:19 +0300, Lucian Cristian wrote:
> > is an annoyance to restart it manually, if you are inside the vpn, you
> > can't do it, I thought that there is a restart script at package update..
>
>
>
> If anyone has a robust/reliable solution that's not likely to cause the
> kinds of problems i'm concerned about, i'd love to hear it.
>
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.
-Reuben
>
[-- Attachment #1.2: Type: text/html, Size: 1330 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2018-11-02 23:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 20:59 wireguard dkms systemd 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 [this message]
2018-11-04 3:24 ` Daniel Kahn Gillmor
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=CALJ2VGaq8AasV99YApW5UWEKK0B-r+uafT7nEjbKARfwADab+A@mail.gmail.com \
--to=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 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.