Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Oliver Freyermuth <freyermuth@physik.uni-bonn.de>,
	 Joshua Sjoding <joshua.sjoding@scjalliance.com>,
	Arlo Clauser <Arlo@starcubedesign.com>,
	 John-Paul Andreini <jandreini@geonerco.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Windows stuck in boot after WireGuard update (switch to WireGuardNT?)
Date: Fri, 24 Sep 2021 11:48:57 -0600	[thread overview]
Message-ID: <CAHmME9oSSzJU4H8jc__HiFsexpB6jJUKM84kN+_9WesoTSMMsQ@mail.gmail.com> (raw)
In-Reply-To: <e0d4dcbb-b0c8-1214-ff0c-c856d168d67f@physik.uni-bonn.de>

Hey guys,

I think we might be onto something with https://w-g.pw/l/ZO5Z ...

I'm going to cut a new release in the next few hours here. When that's
released, would you try updating to 0.4.10, going back to using the
kernel implementation, and letting me know whether the problem
resurfaces? In the absence of being able to locally produce this on a
debuggable machine, I think this kind of trial and error is all we've
got. Hopefully the theory behind https://w-g.pw/l/ZO5Z is correct.

Jason

  parent reply	other threads:[~2021-09-24 17:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-22 10:09 Oliver Freyermuth
     [not found] ` <CAHmME9pgz6PiXdFqcRw90EafHK-Jq9RfcgLUZaJ1ARrtdnjG0w@mail.gmail.com>
2021-09-22 14:02   ` Oliver Freyermuth
2021-09-22 18:57     ` Jason A. Donenfeld
2021-09-22 19:36       ` Joshua Sjoding
2021-09-24  0:21     ` Jason A. Donenfeld
2021-09-24  7:24       ` Oliver Freyermuth
2021-09-24  6:14 ` Jason A. Donenfeld
2021-09-24 17:48 ` Jason A. Donenfeld [this message]
2021-09-24 17:53   ` Joshua Sjoding
2021-09-24 17:57     ` Oliver Freyermuth
2021-09-24 19:59   ` Jason A. Donenfeld
2021-09-24 20:15     ` Arlo Clauser
2021-09-24 20:17       ` John-Paul Andreini
2021-10-14  5:56     ` Jason A. Donenfeld

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=CAHmME9oSSzJU4H8jc__HiFsexpB6jJUKM84kN+_9WesoTSMMsQ@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=Arlo@starcubedesign.com \
    --cc=freyermuth@physik.uni-bonn.de \
    --cc=jandreini@geonerco.com \
    --cc=joshua.sjoding@scjalliance.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).