From: Stephen Hemminger <shemminger@vyatta•com>
To: David Miller <davem@davemloft•net>
Cc: dada1@cosmosbay•com, herbert@gondor•apana.org.au, netdev@vger•kernel.org
Subject: Re: GTSM and TCP accept problem
Date: Sun, 15 Aug 2010 12:38:40 -0400 [thread overview]
Message-ID: <20100815123840.487a5afc@s6510> (raw)
In-Reply-To: <20100814.221258.35029372.davem@davemloft.net>
On Sat, 14 Aug 2010 22:12:58 -0700 (PDT)
David Miller <davem@davemloft•net> wrote:
> From: Stephen Hemminger <shemminger@vyatta•com>
> Date: Sat, 14 Aug 2010 21:46:34 -0400
>
> > The implementation of Generalized TTL Security has a problem
> > on the TCP accept side. Since there can be different number of
> > hops for each peer, the listener ends up doing
> >
> > socket
> > bind
> > set TTL to 255
> > listen
> > while (nfd = accept(peer)) {
> > info = lookup(peer)
> > set MINTTL to 255 - info->ttl_hops
>
> Surely when creating the initial listening socket we should use the
> minimum TTL over the set of peers right?
>
> That surely takes most of the fun out of this problem for the
> attacker.
That only works if all peers are external and using ttl-security.
If any peer is not using ttl-security, then that peer will be
sending with low TTL and the SYN would get dropped.
The real problem goes back to the GTSM RFC assumptions that TTL
security will be done by firewall, not TCP itself.
next prev parent reply other threads:[~2010-08-15 16:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-15 1:46 GTSM and TCP accept problem Stephen Hemminger
2010-08-15 5:12 ` David Miller
2010-08-15 16:38 ` Stephen Hemminger [this message]
2010-08-16 9:43 ` Eric Dumazet
2010-08-18 21:39 ` Stephen Hemminger
2010-08-18 21:48 ` David Miller
2011-10-03 1:46 ` venkatesh natarajan
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=20100815123840.487a5afc@s6510 \
--to=shemminger@vyatta$(echo .)com \
--cc=dada1@cosmosbay$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=herbert@gondor$(echo .)apana.org.au \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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