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:	Thu, 16 Jun 2016 16:50:02 +0200
From:	Hannes Frederic Sowa <hannes@...essinduktion.org>
To:	Daniel Borkmann <daniel@...earbox.net>,
	Derek Ditch <derek.ditch@...il.com>
Cc:	netdev@...r.kernel.org, tom@...bertland.com, jiri@...nulli.us,
	willemb@...gle.com, eric@...it.org
Subject: Re: [Bug 120441] af_packet no longer uses symmetric hashing

On 16.06.2016 16:37, Daniel Borkmann wrote:
> On 06/16/2016 03:57 PM, Derek Ditch wrote:
> [...]
>>> Begin forwarded message:
>>>
>>> From: bugzilla-daemon@...zilla.kernel.org
>>> Subject: [Bug 120441] af_packet no longer uses symmetric hashing
>>> Date: June 16, 2016 at 07:35:54 -0500
>>> To: derek.ditch@...il.com
>>>
>>> https://bugzilla.kernel.org/show_bug.cgi?id=120441
> 
> Just thinking out loud, perhaps one way would be to implement your own
> fanout
> hashing via eBPF demuxer, f.e. in case CPU selection etc wouldn't work.
> Another
> option could be to have a (2nd) customizable hash demux that would
> enforce to
> always go through the flow-dissector and where you would have a socket
> option
> to control keys for it, but I presume that seems rather less desirable.

Isn't a symmetric hashing for af-packet something very fundamental?
Looks much more like a bug to me.

Bye,
Hannes

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ