[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130827125551.GA1195@midget.suse.cz>
Date: Tue, 27 Aug 2013 14:55:51 +0200
From: Jiri Bohac <jbohac@...e.cz>
To: Florian Westphal <fw@...len.de>
Cc: Jiri Bohac <jbohac@...e.cz>, Jakob Lell <jakob@...oblell.com>,
netdev@...r.kernel.org, davem@...emloft.net
Subject: Re: [PATCH 2/3] [RFC] TCP syncookies: introduce sysctl to configure
the MSS tables
On Fri, Aug 16, 2013 at 11:40:57PM +0200, Florian Westphal wrote:
> Jiri Bohac <jbohac@...e.cz> wrote:
> > (compile-tested only)
> >
> > This patch introduces two new sysctls
> > net.ipv4.tcp_syncookies_mss_table
> > net.ipv6.tcp_syncookies_mss_table
> > to manipulate the TCP syncookie MSS tables
>
> The cookie MSS table is small to begin with; trying
> to find values that fit all possible clients is a losing game.
not all servers talk to all the clients. I can imagine some may run very
specific services with very specific packet sizes. Having the MSS
values configurable can't hurt.
> I cannot think of any scenarios where 2 machines, connected
> to internet, could have different mss tables whilst _both_
> improving the default values?
The recently disclosed syncookies vulnerability has differrent
impact on differrent servers.
Some services are secure enough at application level and don't
care at all about TCP connection spoofing. These can use the
sysctl to revert back to the MSS table we have now (or anyting
that better serves their traffic).
Other services are not so secure and some MSS values can be
sacrified to mitigate the risk. With a smaller MSS table, tuning
the values for specific traffic may make even more sense.
--
Jiri Bohac <jbohac@...e.cz>
SUSE Labs, SUSE CZ
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists