All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
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: Sun, 23 Oct 2016 19:23:20 +0900	[thread overview]
Message-ID: <CAHmME9ppmQourShXfNnyOEnH_LdVQHrrc8XCui9MYEVYnTLCiQ@mail.gmail.com> (raw)
In-Reply-To: <87wph0pm06.fsf@toke.dk>

Hi,

I've switched to using the same strategy of tun.c, and simply
resetting all the fields, even if this is semantically incorrect, as
the rest of the kernel seems to do this in fact:
https://git.zx2c4.com/WireGuard/commit/?id=95a869e45905766878cc4fee1a27a1c933786361

This should make WireGuard run fine on PaX. That, combined with the
previous PaX-motivated commit, should make WireGuard work with
Grsecurity kernels without any modification necessary. This work will
be part of the next snapshot I tag.

Jason

      reply	other threads:[~2016-10-23 10:22 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
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 [this message]

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=CAHmME9ppmQourShXfNnyOEnH_LdVQHrrc8XCui9MYEVYnTLCiQ@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=pageexec@gmail.com \
    --cc=re.emese@gmail.com \
    --cc=spender@grsecurity.net \
    --cc=toke@toke.dk \
    --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.