From: Eric Dumazet <eric.dumazet@gmail.com>
To: Zhiyun Qian <zhiyunq@umich.edu>
Cc: netdev@vger.kernel.org
Subject: Re: TCP sequence number inference attack on Linux
Date: Fri, 21 Dec 2012 10:52:11 -0800 [thread overview]
Message-ID: <1356115931.21834.7745.camel@edumazet-glaptop> (raw)
In-Reply-To: <1356114663.21834.7697.camel@edumazet-glaptop>
On Fri, 2012-12-21 at 10:31 -0800, Eric Dumazet wrote:
> I believe RFC 5961 was implemented in recent linux versions.
>
> Is the described vulnerability still present ?
>
By the way, I believe Chrome browser uses private network namespaces,
and statistics are per network namespace, so it should be safe.
next prev parent reply other threads:[~2012-12-21 18:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-21 17:58 TCP sequence number inference attack on Linux Zhiyun Qian
2012-12-21 18:31 ` Eric Dumazet
2012-12-21 18:52 ` Eric Dumazet [this message]
2012-12-21 19:13 ` Zhiyun Qian
2012-12-21 19:30 ` Eric Dumazet
2012-12-22 2:13 ` Hannes Frederic Sowa
2012-12-21 19:10 ` Zhiyun Qian
2012-12-21 19:27 ` Eric Dumazet
2012-12-21 19:49 ` Zhiyun Qian
2012-12-21 22:45 ` Eric Dumazet
2012-12-21 23:52 ` Zhiyun Qian
2012-12-22 0:01 ` Eric Dumazet
2012-12-22 0:04 ` Eric Dumazet
2012-12-22 0:08 ` Zhiyun Qian
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=1356115931.21834.7745.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=zhiyunq@umich.edu \
/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