From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Marco Angaroni <marcoangaroni@gmail.com>
Cc: lvs-devel@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 0/2] netfilter: allow tab character in SIP headers
Date: Wed, 7 Sep 2016 13:56:54 +0200 [thread overview]
Message-ID: <20160907115654.GA4460@salvia> (raw)
In-Reply-To: <20160830165222.pAgDVdNXQ%marcoangaroni@gmail.com>
On Tue, Aug 30, 2016 at 06:52:22PM +0200, Marco Angaroni wrote:
> Current parsing methods for SIP headers do not allow the presence of
> tab characters between header name and header value. As a result Call-ID
> SIP headers like the following are discarded by IPVS SIP persistence
> engine:
>
> "Call-ID\t: mycallid@abcde"
> "Call-ID:\tmycallid@abcde"
>
> In above examples Call-IDs are represented as strings in C language.
> Obviously in real message we have byte "09" before/after colon (":").
>
> Proposed fix is in nf_conntrack_sip module.
> Function sip_skip_whitespace() should skip tabs in addition to spaces,
> since in SIP grammar whitespace (WSP) corresponds to space or tab.
>
> Below is an extract of relevant SIP ABNF syntax.
>
> Call-ID = ( "Call-ID" / "i" ) HCOLON callid
> callid = word [ "@" word ]
>
> HCOLON = *( SP / HTAB ) ":" SWS
> SWS = [LWS] ; sep whitespace
> LWS = [*WSP CRLF] 1*WSP ; linear whitespace
> WSP = SP / HTAB
> word = 1*(alphanum / "-" / "." / "!" / "%" / "*" /
> "_" / "+" / "`" / "'" / "~" /
> "(" / ")" / "<" / ">" /
> ":" / "\" / DQUOTE /
> "/" / "[" / "]" / "?" /
> "{" / "}" )
Applied this one too. I got confused because patch 0/x is usually the
cover letter, I suggest you don't use 0/x for patch series in the future.
Thanks!
next prev parent reply other threads:[~2016-09-07 11:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 16:52 [PATCH 0/2] netfilter: allow tab character in SIP headers Marco Angaroni
2016-09-07 11:56 ` Pablo Neira Ayuso [this message]
2016-09-07 20:00 ` Marco Angaroni
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=20160907115654.GA4460@salvia \
--to=pablo@netfilter.org \
--cc=lvs-devel@vger.kernel.org \
--cc=marcoangaroni@gmail.com \
--cc=netfilter-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.