All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [WireGuard] [PATCH 3/4] Explain the optional nature of Peer.EndPoint more clearly
Date: Fri, 1 Jul 2016 04:08:08 +0200	[thread overview]
Message-ID: <CAHmME9p79wUVkdUX30dgrJ28rMkX13ywAi-4OBg+agiZdEijQQ@mail.gmail.com> (raw)
In-Reply-To: <1467327323-8532-3-git-send-email-dkg@fifthhorseman.net>

I'm merging a commit with some of these suggested changes for 1,2,4.
Thanks for those. But the changes here are simply not correct.

The endpoint is simply the initial endpoint used to contact the peer.
If the peer sends legit traffic from a different endpoint, it will be
updated to that new endpoint. So, specifying an endpoint doesn't bind
traffic to that endpoint. It's simply an initial specifier of it.
Otherwise, how does traffic get started flowing?

  reply	other threads:[~2016-07-01  2:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-30 22:55 [WireGuard] [PATCH 1/4] address:port separation uses colon, not comma Daniel Kahn Gillmor
2016-06-30 22:55 ` [WireGuard] [PATCH 2/4] explain "security reasons" Daniel Kahn Gillmor
2016-06-30 22:55 ` [WireGuard] [PATCH 3/4] Explain the optional nature of Peer.EndPoint more clearly Daniel Kahn Gillmor
2016-07-01  2:08   ` Jason A. Donenfeld [this message]
2016-07-01 12:13     ` Daniel Kahn Gillmor
2016-07-01 20:54       ` Jason A. Donenfeld
2016-06-30 22:55 ` [WireGuard] [PATCH 4/4] Clarify what Peer.AllowedIPs actually constrains Daniel Kahn Gillmor

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=CAHmME9p79wUVkdUX30dgrJ28rMkX13ywAi-4OBg+agiZdEijQQ@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=dkg@fifthhorseman.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 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.