netdev - Re: [PATCH RFC 0/6] SYNPROXY target v2

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:	Mon, 26 Aug 2013 16:24:49 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	kaber@...sh.net
Cc:	pablo@...filter.org, netfilter-devel@...r.kernel.org,
	netdev@...r.kernel.org, mph@....com, jesper.brouer@...il.com,
	as@....com
Subject: Re: [PATCH RFC 0/6] SYNPROXY target v2

From: Patrick McHardy <kaber@...sh.net>
Date: Fri, 23 Aug 2013 09:52:03 +0200

> The following patches contain the current version of the SYNPROXY target.
> Changes this the last posting are:
> 
> - use sysctl_ip_default_ttl instead of hardcoding 64
> 
> - use MAX_TCP_HEADER instead of LL_MAX_HEADER
> 
> - add some comments requested by Jesper regarding ack_seq initialization
>   in the server's SYN packet
> 
> - use consume_skb() instead of kfree_skb() in the synproxy hook
> 
> - remove a fixme and add explicit check for "-p tcp" in the SYNPROXY rule
>   in the IPv6 version
> 
> - some whitespace fixes
> 
> - a larger number of fixes for properly handling retransmissions and
>   out of order packets, please see the changelog included in patch 6/6
>   for details.
>   
>   I've kept those in a seperate patch for now to ease review, we'll do
>   some more extensive testing on monday and I'll fold the changes in
>   their respective patches before the final submission.
> 
> Comments welcome.

No objections to the non-netfilter portions:

Acked-by: David S. Miller <davem@...emloft.net>
--
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