From: Florian Westphal <fw@strlen.de>
To: "İbrahim Ercan" <ibrahim.metu@gmail.com>
Cc: Florian Westphal <fw@strlen.de>,
netfilter@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: Is this possible SYN Proxy bug?
Date: Tue, 18 Jun 2019 14:40:26 +0200 [thread overview]
Message-ID: <20190618124026.4kvpdkbstdgaluij@breakpoint.cc> (raw)
In-Reply-To: <CAK6Qs9mTkAaH9+RqzmtrbNps1=NtW4c8wtJy7Kjay=r7VSJwsQ@mail.gmail.com>
İbrahim Ercan <ibrahim.metu@gmail.com> wrote:
> On Tue, Jun 18, 2019 at 2:59 PM Florian Westphal <fw@strlen.de> wrote:
>
> > >
> > > I am confused. So this statement from manual page is just a illusion?
> > > --mss maximum segment size
> > > Maximum segment size announced to clients. This must
> > > match the backend.
> >
> > ?
> >
> > Your question was about MSS sent to server.
> >
> > Flow is this:
> > Client Synproxy Server
> > -> Syn, mss X
> > <-Synack,mss M
> > -> ACK
> > -> Syn, mss Y
> >
> > M is what you need to configure via --mss switch.
> >
> > Because Synproxy keeps no state, it can only send
> > to real server the MSS that was encoded in syncookie (in synack)
> > packet. Therefore, X == Y only if the Value from client matches
> > exactly one for the four values of the mss table, in all other
> > cases Y is the next lowest available one. In your case thats 536.
> >
> > > I don't understand why these restriction exist. Why can't we set mss
> > > value same as what client send to us?
> >
> > We only have 2 bits out of the 32Bit Sequence number for MSS. Increasing
> > mss state table reduces security margin of the cookie.
>
> My question about both way actually. If you check out my tests, M is
> also not correct. Client sends mss 1260 and syn proxy responds 1260
> too although I set mss 1460 in iptables.
Does this patch fix the problem for you?
diff --git a/net/ipv4/netfilter/ipt_SYNPROXY.c b/net/ipv4/netfilter/ipt_SYNPROXY.c
--- a/net/ipv4/netfilter/ipt_SYNPROXY.c
+++ b/net/ipv4/netfilter/ipt_SYNPROXY.c
@@ -286,6 +286,7 @@ synproxy_tg4(struct sk_buff *skb, const struct xt_action_param *par)
opts.options |= XT_SYNPROXY_OPT_ECN;
opts.options &= info->options;
+ opts.mss = info->mss;
if (opts.options & XT_SYNPROXY_OPT_TIMESTAMP)
synproxy_init_timestamp_cookie(info, &opts);
else
diff --git a/net/ipv6/netfilter/ip6t_SYNPROXY.c b/net/ipv6/netfilter/ip6t_SYNPROXY.c
--- a/net/ipv6/netfilter/ip6t_SYNPROXY.c
+++ b/net/ipv6/netfilter/ip6t_SYNPROXY.c
@@ -300,6 +300,7 @@ synproxy_tg6(struct sk_buff *skb, const struct xt_action_param *par)
opts.options |= XT_SYNPROXY_OPT_ECN;
opts.options &= info->options;
+ opts.mss = info->mss;
if (opts.options & XT_SYNPROXY_OPT_TIMESTAMP)
synproxy_init_timestamp_cookie(info, &opts);
else
next prev parent reply other threads:[~2019-06-18 12:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 10:06 Is this possible SYN Proxy bug? İbrahim Ercan
2019-06-18 10:40 ` Florian Westphal
2019-06-18 11:40 ` İbrahim Ercan
2019-06-18 11:59 ` Florian Westphal
2019-06-18 12:07 ` İbrahim Ercan
2019-06-18 12:40 ` Florian Westphal [this message]
2019-06-19 9:26 ` İbrahim Ercan
2019-06-21 7:00 ` İbrahim Ercan
2019-06-21 11:10 ` Florian Westphal
2019-06-24 7:55 ` İbrahim Ercan
2019-06-24 8:09 ` Fernando Fernandez Mancera
2019-06-24 10:20 ` Florian Westphal
2019-06-24 12:35 ` İbrahim Ercan
2019-06-24 13:32 ` Florian Westphal
[not found] ` <OFD1A8080A.6956CA33-ON0025841D.003AFD98-C125841D.003BC900@notes.na.collabserv.com>
2019-06-18 11:50 ` İbrahim Ercan
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=20190618124026.4kvpdkbstdgaluij@breakpoint.cc \
--to=fw@strlen.de \
--cc=ibrahim.metu@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.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).