From: Alexander Holler <holler@ahsoftware.de>
To: Martin KaFai Lau <kafai@fb.com>, netdev <netdev@vger.kernel.org>
Cc: David Miller <davem@davemloft.net>,
Hannes Frederic Sowa <hannes@stressinduktion.org>,
Julian Anastasov <ja@ssi.bg>,
Steffen Klassert <steffen.klassert@secunet.com>,
Kernel Team <Kernel-team@fb.com>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v5 00/11] ipv6: Only create RTF_CACHE route after encountering pmtu exception
Date: Mon, 17 Aug 2015 11:43:20 +0200 [thread overview]
Message-ID: <55D1ACB8.3040500@ahsoftware.de> (raw)
In-Reply-To: <55CEEECA.8000702@ahsoftware.de>
Am 15.08.2015 um 09:48 schrieb Alexander Holler:
> Am 30.07.2015 um 13:57 schrieb Alexander Holler:
>> Am 29.07.2015 um 11:25 schrieb Alexander Holler:
>>> Am 23.05.2015 um 05:55 schrieb Martin KaFai Lau:
> To complete the discussion, that "annoying behaviour" is also a big
> information leak.
>
> Because routes aren't considered confidential and aren't subject to
> privacy, that broken behaviour enabled *everyone* on the same system to
> see *all* the remote IPv6 systems to which there have been connection
> establishment tries.
Just in case I haven't described the problem I see clearly enough:
"Everyone" means everything (other SW) too, and if "Happy_Eyeballs"
algorithms are used (see RFC 6555), this also affects systems which only
have an IPv4 connection to the world, as long as IPv6 is enabled.
That means it does not only affect multiuser systems and the current
behaviour of kernels < 4.2 renders e.g. the private mode of most
browsers somewhat useless too (in regard to protection against other SW
and/or users running on the same system).
That's why I vote to check out if it's possible/reasonable to backport
this series to the stable kernels.
Regards,
Alexander Holler
next prev parent reply other threads:[~2015-08-17 9:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1432353366-2296465-1-git-send-email-kafai@fb.com>
[not found] ` <55B89C14.2070700@ahsoftware.de>
[not found] ` <55BA1144.9090203@ahsoftware.de>
2015-08-15 7:48 ` [PATCH net-next v5 00/11] ipv6: Only create RTF_CACHE route after encountering pmtu exception Alexander Holler
2015-08-17 9:43 ` Alexander Holler [this message]
2015-08-28 7:36 ` Martin KaFai Lau
2015-08-28 9:27 ` Alexander Holler
2015-08-28 9:34 ` Alexander Holler
2015-08-28 18:27 ` David Miller
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=55D1ACB8.3040500@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=Kernel-team@fb.com \
--cc=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--cc=ja@ssi.bg \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=steffen.klassert@secunet.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).