netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: roland@purestorage.com
Cc: johnwheffner@gmail.com, mj@ucw.cz, netdev@vger.kernel.org
Subject: Re: ipv4: Simplify ARP hash function.
Date: Fri, 08 Jul 2011 12:27:42 -0700 (PDT)	[thread overview]
Message-ID: <20110708.122742.1006323245708104141.davem@davemloft.net> (raw)
In-Reply-To: <CAL1RGDWbCi_nE8tRp9zyX3Z1yBHKP9ygxNV6TNKp4Up+0g2EPA@mail.gmail.com>

From: Roland Dreier <roland@purestorage.com>
Date: Fri, 8 Jul 2011 12:26:17 -0700

> On Fri, Jul 8, 2011 at 11:06 AM, David Miller <davem@davemloft.net> wrote:
>> Ok, there was also an unintended bug in my original patch,
>> I lost the bottom 8 bits in the fold, the hash function
>> should instead be:
>>
>> +static inline u32 arp_hashfn(u32 key, const struct net_device *dev, u32 hash_rnd)
>> +{
>> +       u32 val = key ^ dev->ifindex ^ hash_rnd;
>> +
>> +       return val ^ (val >> 8) ^ (val >> 16) ^ (val >> 24);
>> +}
> 
> Doesn't seem to matter much -- this is now equivalent to
> 
>       a = key ^ dev->ifindex
>        return (a ^ (a >> 8) ^ (a >> 16) ^ (a >> 24))           // (1)
>             ^ (rnd ^ (rnd >> 8) ^ (rnd >> 16) ^ (rnd >> 24))   // (2)
> 
> where again the attacker controls (1), and (2) is a constant.

Right, but how can you attack it?  Show me how you can grow
a hash chain of arbitrary length by modulating the key in
a deterministic way.

Nobody has done this yet.

  reply	other threads:[~2011-07-08 19:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-08 17:10 ipv4: Simplify ARP hash function David Miller
2011-07-08 17:40 ` Martin Mares
2011-07-08 17:47   ` David Miller
2011-07-08 17:54     ` David Miller
2011-07-08 18:03     ` John Heffner
2011-07-08 18:06       ` David Miller
2011-07-08 19:26         ` Roland Dreier
2011-07-08 19:27           ` David Miller [this message]
2011-07-08 19:39             ` Michał Mirosław
2011-07-08 19:51               ` David Miller
2011-07-08 19:59                 ` David Miller
2011-07-08 20:10                   ` Michał Mirosław
2011-07-08 20:34                     ` Michał Mirosław
2011-07-08 20:35                       ` David Miller
2011-07-08 20:44             ` Roland Dreier
2011-07-08 22:32               ` David Miller
2011-07-08 23:11                 ` Roland Dreier
2011-07-10 19:07                   ` David Miller
2011-07-08 23:41                 ` Stephen Hemminger
2011-07-08 23:47                   ` David Miller
2011-07-09  3:08                     ` Stephen Hemminger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110708.122742.1006323245708104141.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=johnwheffner@gmail.com \
    --cc=mj@ucw.cz \
    --cc=netdev@vger.kernel.org \
    --cc=roland@purestorage.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).