netdev - Re: [PATCH net] sctp: asconf process should treat multiple address parameter as unrecognized parameter

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CADvbK_cM2u452XWWdHggrCu7f+_v80Ucb3XMAJqeqCjBjwQjJw@mail.gmail.com>
Date:	Tue, 25 Aug 2015 20:43:10 +0800
From:	lucien xin <lucien.xin@...il.com>
To:	vyasevic@...hat.com
Cc:	network dev <netdev@...r.kernel.org>,
	Marcelo Ricardo Leitner <mleitner@...hat.com>,
	davem <davem@...emloft.net>
Subject: Re: [PATCH net] sctp: asconf process should treat multiple address
 parameter as unrecognized parameter

On Tue, Aug 25, 2015 at 8:39 PM, lucien xin <lucien.xin@...il.com> wrote:
>>
>> I think it would be much better to catch this in the validation stage.
>> If an implementation inserts multiple address parameters, we don't really know
>> which one we should be using.
>>
>
> the params of ASCONF chunk should consist of one *Address Parameter* and one
> or more *ASCONF Parameters*. besides, the address parameter should be in the
> beginning. so the first one must be our choice.
>
> if we cat this in the validation stage, I think it will be hard to treat it as a
> unrecognized parameter,
because *unrecognized parameter* cause packet need to be built in
sctp_process_asconf(),
as current linux's implementation.
--
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