From: Luiz Angelo Daros de Luca <luizluca@gmail.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: passing-through TOS/DSCP marking
Date: Tue, 6 Jul 2021 17:08:00 -0300 [thread overview]
Message-ID: <CAJq09z5fhE=Rj_wTs5x1zYSu3e0+tU-huymEVV5Y6Bfyu_7fJw@mail.gmail.com> (raw)
In-Reply-To: <0102017a7a9e0329-2cf98ec6-3874-4f0e-80f0-663792b43e3b-000000@eu-west-1.amazonses.com>
I see talented people spending resources trying to go around a
wireguard design decision. I understand that wireguard try to keep it
as safe as possible and as simple as possible. However, passing some
traffic information to the encrypted packet is a requirement for some
setups. Wouldn't it be better to have it provided by wireguard but
disabled by default? If the change don't kill a kitty, it will not
harm the security as users are already doing the same but through a
much harder way.
My 2 cents.
---
Luiz Angelo Daros de Luca
luizluca@gmail.com
prev parent reply other threads:[~2021-07-06 20:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 13:24 Daniel Golle
2021-06-16 16:28 ` Jason A. Donenfeld
2021-06-16 19:26 ` Daniel Golle
2021-06-16 23:33 ` Toke Høiland-Jørgensen
2021-06-17 7:55 ` Florent Daigniere
2021-06-17 9:41 ` Daniel Golle
2021-06-17 12:24 ` Toke Høiland-Jørgensen
[not found] ` <CAMaqUZ09KRtp01OK3u-Di52X_kH9eT4E-wmnPc6QzjSCd5dEiw@mail.gmail.com>
2021-06-17 20:54 ` Toke Høiland-Jørgensen
2021-06-17 23:04 ` Toke Høiland-Jørgensen
2021-06-18 12:24 ` Jason A. Donenfeld
2021-06-21 12:36 ` Daniel Golle
2021-06-21 14:27 ` Toke Høiland-Jørgensen
2021-06-30 17:23 ` Daniel Golle
2021-06-30 20:55 ` Toke Høiland-Jørgensen
2021-07-04 14:15 ` Daniel Golle
2021-07-05 15:21 ` Toke Høiland-Jørgensen
2021-07-05 16:05 ` Daniel Golle
2021-07-05 16:59 ` Toke Høiland-Jørgensen
2021-07-05 17:26 ` Daniel Golle
2021-07-05 21:20 ` Toke Høiland-Jørgensen
2021-07-06 7:00 ` Florent Daigniere
2021-07-06 20:08 ` Luiz Angelo Daros de Luca [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='CAJq09z5fhE=Rj_wTs5x1zYSu3e0+tU-huymEVV5Y6Bfyu_7fJw@mail.gmail.com' \
--to=luizluca@gmail.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).