From: Oliver Freyermuth <freyermuth@physik.uni-bonn.de>
To: Joshua Sjoding <joshua.sjoding@scjalliance.com>,
"Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Arlo Clauser <Arlo@starcubedesign.com>,
John-Paul Andreini <jandreini@geonerco.com>,
WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Windows stuck in boot after WireGuard update (switch to WireGuardNT?)
Date: Fri, 24 Sep 2021 19:57:35 +0200 [thread overview]
Message-ID: <adac36f3-e33c-606e-d287-c11467b70606@physik.uni-bonn.de> (raw)
In-Reply-To: <CALaUSusvu8iJTXNc_07=tQ=yNKJ+HXOe1J5A=HRyAAJbzDjjYg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1149 bytes --]
Awesome indeed :-).
I'll contact our two affected users once 0.4.10 is released, especially the one who managed to trigger it twice in one week
should be a good test candidate.
Cheers and a nice weekend,
Oliver
Am 24.09.21 um 19:53 schrieb Joshua Sjoding:
> Awesome! Can do. Thanks Jason!
>
> Joshua Sjoding
> SCJ Alliance
> IT Specialist
>
> On Fri, Sep 24, 2021 at 10:49 AM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>>
>> 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
--
Oliver Freyermuth
Universität Bonn
Physikalisches Institut, Raum 1.047
Nußallee 12
53115 Bonn
--
Tel.: +49 228 73 2367
Fax: +49 228 73 7869
--
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5432 bytes --]
next prev parent reply other threads:[~2021-09-24 20:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 10:09 Windows stuck in boot after WireGuard update (switch to WireGuardNT?) 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
2021-09-24 17:53 ` Joshua Sjoding
2021-09-24 17:57 ` Oliver Freyermuth [this message]
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=adac36f3-e33c-606e-d287-c11467b70606@physik.uni-bonn.de \
--to=freyermuth@physik.uni-bonn.de \
--cc=Arlo@starcubedesign.com \
--cc=Jason@zx2c4.com \
--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 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.