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: <20170223.120124.846549814513489060.davem@davemloft.net>
Date:   Thu, 23 Feb 2017 12:01:24 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     laforge@...monks.org
Cc:     tom@...bertland.com, pablo@...filter.org, aschultz@...p.net,
        gerlitz.or@...il.com, ogerlitz@...lanox.com, jhs@...atatu.com,
        netdev@...r.kernel.org, timo.lindhorst@...velping.com
Subject: Re: [PATCH net-next] net/gtp: Add udp source port generation
 according to flow hash

From: Harald Welte <laforge@...monks.org>
Date: Thu, 23 Feb 2017 17:50:51 +0100

> I understand and support the motivation to design robust systsems even
> in the presence of broken/ignorant specs, but I think this is one of the
> situations where it is useless (and IMHO impossible) to do anything
> about it.

I think avoiding trying to do something reasonable about this and just
saying "this is how cellular networks are" is not acceptable.

We know how to properly strengthen tunnelling implementations in the
kernel against DDoS attachs, GTP can be treated similarly.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ