From: Xin Long <lucien.xin@gmail.com>
To: network dev <netdev@vger.kernel.org>, linux-sctp@vger.kernel.org
Cc: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
Neil Horman <nhorman@tuxdriver.com>,
davem@davemloft.net
Subject: [PATCH net-next 0/3] sctp: add proper process for duplicated stream reconf requests
Date: Sat, 15 Apr 2017 14:00:26 +0000 [thread overview]
Message-ID: <cover.1492264734.git.lucien.xin@gmail.com> (raw)
Now sctp stream reconf will process a request again even if it's seqno
is less than asoc->strreset_inseq. It may cause a replay attack.
This patchset is to avoid it by add proper process for all duplicated
stream reconf requests.
Xin Long (3):
sctp: process duplicated strreset out and addstrm out requests
correctly
sctp: process duplicated strreset in and addstrm in requests correctly
sctp: process duplicated strreset asoc request correctly
include/net/sctp/structs.h | 1 +
net/sctp/stream.c | 96 +++++++++++++++++++++++++++++++++++-----------
2 files changed, 74 insertions(+), 23 deletions(-)
--
2.1.0
WARNING: multiple messages have this Message-ID (diff)
From: Xin Long <lucien.xin@gmail.com>
To: network dev <netdev@vger.kernel.org>, linux-sctp@vger.kernel.org
Cc: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
Neil Horman <nhorman@tuxdriver.com>,
davem@davemloft.net
Subject: [PATCH net-next 0/3] sctp: add proper process for duplicated stream reconf requests
Date: Sat, 15 Apr 2017 22:00:26 +0800 [thread overview]
Message-ID: <cover.1492264734.git.lucien.xin@gmail.com> (raw)
Now sctp stream reconf will process a request again even if it's seqno
is less than asoc->strreset_inseq. It may cause a replay attack.
This patchset is to avoid it by add proper process for all duplicated
stream reconf requests.
Xin Long (3):
sctp: process duplicated strreset out and addstrm out requests
correctly
sctp: process duplicated strreset in and addstrm in requests correctly
sctp: process duplicated strreset asoc request correctly
include/net/sctp/structs.h | 1 +
net/sctp/stream.c | 96 +++++++++++++++++++++++++++++++++++-----------
2 files changed, 74 insertions(+), 23 deletions(-)
--
2.1.0
next reply other threads:[~2017-04-15 14:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-15 14:00 Xin Long [this message]
2017-04-15 14:00 ` [PATCH net-next 0/3] sctp: add proper process for duplicated stream reconf requests Xin Long
2017-04-15 14:00 ` [PATCH net-next 1/3] sctp: process duplicated strreset out and addstrm out requests correctly Xin Long
2017-04-15 14:00 ` Xin Long
2017-04-15 14:00 ` [PATCH net-next 2/3] sctp: process duplicated strreset in and addstrm in " Xin Long
2017-04-15 14:00 ` Xin Long
2017-04-15 14:00 ` [PATCH net-next 3/3] sctp: process duplicated strreset asoc request correctly Xin Long
2017-04-15 14:00 ` Xin Long
2017-04-18 17:40 ` [PATCH net-next 0/3] sctp: add proper process for duplicated stream reconf requests David Miller
2017-04-18 17:40 ` David Miller
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=cover.1492264734.git.lucien.xin@gmail.com \
--to=lucien.xin@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
/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.