From: Vasili Pupkin <diggest@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Linux kernel 5 different behavior
Date: Mon, 26 Aug 2019 12:29:53 +0300 [thread overview]
Message-ID: <CANH_QeZs5BhNumC6tDO=QiNARVbW02L8wRx=r-XLGNE-8u8c3A@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9pLLpPTJ+f2r0t0gh08nTrKZ8qGLgoL4o5NFoaUj_1KGQ@mail.gmail.com>
On Mon, Aug 26, 2019 at 5:09 AM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> > Usage of fwmark is my current workaround. If the same user id of an
> > outer packets is not a bug then ignore it.
>
> I can see arguments both ways. Do you recall off hand the last kernel
> version that had the prior behavior? I'd like to try to find the
> commit and read the rationale upstream.
I see the difference now between 4.18.0 and 5.0.0 kernels, the closest
I can get with readily compiled kernels on my distro. According to
`iptables -t mangle -A OUTPUT -j LOG --log-uid` on kernel 4.18 outer
packets have UID=0 if original packets were sent from system processes
and do not have associated UID at all if original packets were sent by
the user. On kernel 5.0 they always inherit UID.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2019-08-26 12:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-25 16:59 Linux kernel 5 different behavior Vasili Pupkin
2019-08-25 18:52 ` Jason A. Donenfeld
2019-08-25 19:03 ` Vasili Pupkin
2019-08-25 19:07 ` Jason A. Donenfeld
2019-08-25 20:04 ` Vasili Pupkin
2019-08-26 2:08 ` Jason A. Donenfeld
2019-08-26 9:29 ` Vasili Pupkin [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='CANH_QeZs5BhNumC6tDO=QiNARVbW02L8wRx=r-XLGNE-8u8c3A@mail.gmail.com' \
--to=diggest@gmail.com \
--cc=Jason@zx2c4.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).