netdev - Re: [PATCH 2/4] dccp: Implement both feature-local and feature-remote Sequence Window feature

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]

Date:	Sun, 18 Jan 2009 21:40:08 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	gerrit@....abdn.ac.uk
Cc:	dccp@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH 2/4] dccp: Implement both feature-local and
 feature-remote Sequence Window feature

From: Gerrit Renker <gerrit@....abdn.ac.uk>
Date: Sat, 17 Jan 2009 10:36:31 +0100

> This adds full support for local/remote Sequence Window feature, from which the 
>   * sequence-number-validity (W) and 
>   * acknowledgment-number-validity (W') windows 
> derive as specified in RFC 4340, 7.5.3. 
> 
> Specifically, the following is contained in this patch:
>   * integrated new socket fields into dccp_sk;
>   * updated the update_gsr/gss routines with regard to these fields;
>   * updated handler code: the Sequence Window feature is located at the TX side,
>     so the local feature is meant if the handler-rx flag is false;
>   * the initialisation of `rcv_wnd' in reqsk is removed, since
>     - rcv_wnd is not used by the code anywhere;
>     - sequence number checks are not done in the LISTEN state (cf. 7.5.3);
>     - dccp_check_req checks the Ack number validity more rigorously;
>   * the `struct dccp_minisock' became empty and is now removed.
> 
> Signed-off-by: Gerrit Renker <gerrit@....abdn.ac.uk>
> Acked-by: Ian McDonald <ian.mcdonald@...di.co.nz>

Applied for 2.6.30
--
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