From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Emese Revfy <re.emese@gmail.com>, Pipacs <pageexec@gmail.com>,
Brad Spengler <spender@grsecurity.net>,
WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [WireGuard] Error building against grsec-enabled kernel
Date: Fri, 21 Oct 2016 11:53:14 +0200 [thread overview]
Message-ID: <87bmyet4dx.fsf@toke.dk> (raw)
In-Reply-To: <CAHmME9oAnWiN8fx5dGP6+i+rTdxH4fMfxmbsr56Ey7viBwiL-Q@mail.gmail.com> (Jason A. Donenfeld's message of "Fri, 21 Oct 2016 17:47:52 +0900")
"Jason A. Donenfeld" <Jason@zx2c4.com> writes:
> On Fri, Oct 21, 2016 at 5:02 PM, PaX Team <pageexec@gmail.com> wrote:
>> are you sure it was for satisfying PaX only and not a bug itself? :)
>
> Blurg. I was overly hasty. Note to self: do not prepare conf
> presentations and push code at the same time. Indeed this /should/ be
> ~0, which means "unset". I can't see any bugs by making it 0, but it
> would make things "semantically incorrect", I think.
>
> So the bug is actually in the ipv6 fragmentation code. I just sent a
> patch upstream and CC'd you and Emese.
Wooh! FYI I was seeing the bug being triggered on IPv4 as well...
-Toke
next prev parent reply other threads:[~2016-10-21 9:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 13:03 [WireGuard] Error building against grsec-enabled kernel Toke Høiland-Jørgensen
2016-10-19 14:18 ` Toke Høiland-Jørgensen
2016-10-19 16:07 ` Toke Høiland-Jørgensen
2016-10-19 22:35 ` Jason A. Donenfeld
2016-10-20 2:19 ` Jason A. Donenfeld
2016-10-21 0:24 ` PaX Team
2016-10-21 2:32 ` Jason A. Donenfeld
2016-10-21 8:02 ` PaX Team
2016-10-21 8:47 ` Jason A. Donenfeld
2016-10-21 9:46 ` PaX Team
2016-10-22 7:56 ` Jason A. Donenfeld
2016-10-21 9:53 ` Toke Høiland-Jørgensen [this message]
2016-10-22 8:03 ` Jason A. Donenfeld
2016-10-22 13:10 ` Toke Høiland-Jørgensen
2016-10-23 10:23 ` 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=87bmyet4dx.fsf@toke.dk \
--to=toke@toke.dk \
--cc=Jason@zx2c4.com \
--cc=pageexec@gmail.com \
--cc=re.emese@gmail.com \
--cc=spender@grsecurity.net \
--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