From: David Miller <davem@davemloft.net>
To: vladislav.yasevich@hp.com
Cc: netdev@vger.kernel.org, lksctp-developers@lists.sourceforge.net
Subject: Re: [PATCH 2/3] [SCTP]: Correctly handle AUTH parameters in unexpected INIT
Date: Mon, 07 Jan 2008 00:27:53 -0800 (PST) [thread overview]
Message-ID: <20080107.002753.188675425.davem@davemloft.net> (raw)
In-Reply-To: <1199475946-11103-3-git-send-email-vladislav.yasevich@hp.com>
From: Vlad Yasevich <vladislav.yasevich@hp.com>
Date: Fri, 4 Jan 2008 14:45:45 -0500
> When processing an unexpected INIT chunk, we do not need to
> do any preservation of the old AUTH parameters. In fact,
> doing such preservations will nullify AUTH and allow connection
> stealing.
>
> Signed-off-by: Vlad Yasevich <vladislav.yasevich@hp.com>
Applied.
next prev parent reply other threads:[~2008-01-07 8:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-04 19:45 [PATCH 0/3] [SCTP] AUTH Bug fixes Vlad Yasevich
2008-01-04 19:45 ` [PATCH 1/3] [SCTP]: Fix the name of the authentication event Vlad Yasevich
2008-01-07 8:27 ` David Miller
2008-01-04 19:45 ` [PATCH 2/3] [SCTP]: Correctly handle AUTH parameters in unexpected INIT Vlad Yasevich
2008-01-07 8:27 ` David Miller [this message]
2008-01-04 19:45 ` [PATCH 3/3] [SCTP]: Add back the code that accounted for FORWARD_TSN parameter in INIT Vlad Yasevich
2008-01-07 8:28 ` 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=20080107.002753.188675425.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=lksctp-developers@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=vladislav.yasevich@hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox