netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Tom Herbert <tom@herbertland.com>,
	Sowmini Varadhan <sowmini.varadhan@oracle.com>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>,
	Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>
Subject: Re: IPv6 extension header privileges
Date: Fri, 27 May 2016 18:46:45 +0200	[thread overview]
Message-ID: <1464367605.681310.620746281.74E342B0@webmail.messagingengine.com> (raw)
In-Reply-To: <CALx6S3580cJPWskNYD_xYbveXTdOzPVB8axXh471jDVzm94PhA@mail.gmail.com>

On Thu, May 26, 2016, at 20:42, Tom Herbert wrote:
> Thinking about this some more, the per option white list is a better
> approach. If we allow an open ended mechanism for applications to
> signal the network with arbitrary data (like user specified hbp
> options would be), then use of that mechanism will inevitably
> exploited by some authorities to force user to hand over private data
> about their communications. It's better to not build in back doors to
> security...

Also I don't think that HbH options form some kind of hidden covert
channel. They mostly appear by unused fields which cannot be verified by
the other (receiving) side in any way.

  parent reply	other threads:[~2016-05-27 16:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-20 22:37 IPv6 extension header privileges Tom Herbert
2016-05-21  0:20 ` Hannes Frederic Sowa
2016-05-21  1:56   ` Sowmini Varadhan
2016-05-21  9:34     ` Hannes Frederic Sowa
2016-05-21 10:02       ` Sowmini Varadhan
2016-05-21 15:19       ` Tom Herbert
2016-05-21 15:33         ` Hannes Frederic Sowa
2016-05-21 16:00           ` Tom Herbert
2016-05-21 16:16             ` Hannes Frederic Sowa
2016-05-21 17:46               ` Sowmini Varadhan
2016-05-22  1:08                 ` Hannes Frederic Sowa
2016-05-22 11:56                   ` Sowmini Varadhan
2016-05-22 12:13                     ` Hannes Frederic Sowa
2016-05-23 18:11                     ` Tom Herbert
2016-05-26 18:42                       ` Tom Herbert
2016-05-27  9:53                         ` Hannes Frederic Sowa
2016-05-27 15:03                           ` Sowmini Varadhan
2016-05-27 16:59                             ` Tom Herbert
2016-05-27 17:14                               ` Hannes Frederic Sowa
2016-05-27 17:38                                 ` Tom Herbert
2016-05-27 16:46                         ` Hannes Frederic Sowa [this message]
2016-05-27 17:05                           ` Tom Herbert
2016-05-21 16:28             ` Hannes Frederic Sowa
2016-05-27  3:37 ` YOSHIFUJI Hideaki

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=1464367605.681310.620746281.74E342B0@webmail.messagingengine.com \
    --to=hannes@stressinduktion.org \
    --cc=netdev@vger.kernel.org \
    --cc=sowmini.varadhan@oracle.com \
    --cc=tom@herbertland.com \
    --cc=yoshfuji@linux-ipv6.org \
    /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).