From: Eric Dumazet <eric.dumazet@gmail.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
kuznet@ms2.inr.ac.ru, jmorris@namei.org, yoshfuji@linux-ipv6.org,
kaber@trash.net
Subject: Re: [PATCH] ipv4: remove ip_rt_secret timer
Date: Thu, 06 May 2010 22:10:14 +0200 [thread overview]
Message-ID: <1273176614.2222.21.camel@edumazet-laptop> (raw)
In-Reply-To: <20100506195442.GC5063@hmsreliant.think-freely.org>
> Doing that doesn't solve my aim however, which is to avoid performing rt_genid
> updates when no one is attacking you at all. I completely agree that we can
> start the gen_id at some random value (by forcing an initial invalidation),
> however. Beyond that however, if someone is managing to guess our secret value,
> then we need to make our secret value more complex to determine. Perhaps given
> the reduction in the number of times we need to iterate our gen_id with the
> timer gone, we can use something more heavyweight to determine the the hash
> secret (the cprng perhaps?).
Secrets that dont change are known to be honey pots for hackers.
I just dont see why we want to risk security regressions for something
that proved to work well.
Cache invalidation is just a genid change nowadays, and dont have side
effects.
Considering we do cache invalidation when routes are changed anyway, I
dont get why we should avoid the invalidation once every xxx seconds...
If you believe this cache invalidation has problems, maybe we should
address them and not hide them ?
next prev parent reply other threads:[~2010-05-06 20:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 17:16 [PATCH] ipv4: remove ip_rt_secret timer Neil Horman
2010-05-06 17:32 ` Eric Dumazet
2010-05-06 18:02 ` Neil Horman
2010-05-06 18:33 ` Eric Dumazet
2010-05-06 19:54 ` Neil Horman
2010-05-06 20:10 ` Eric Dumazet [this message]
2010-05-06 20:25 ` Neil Horman
2010-05-06 20:29 ` [PATCH] ipv4: remove ip_rt_secret timer (v2) Neil Horman
2010-05-06 21:08 ` Eric Dumazet
2010-05-07 0:02 ` nhorman
2010-05-07 19:55 ` [PATCH] ipv4: remove ip_rt_secret timer (v3) Neil Horman
2010-05-07 21:04 ` Eric Dumazet
2010-05-07 23:15 ` Neil Horman
2010-05-08 1:01 ` [PATCH] ipv4: remove ip_rt_secret timer (v4) Neil Horman
2010-05-08 6:36 ` Eric Dumazet
2010-05-08 8:58 ` David Miller
2010-05-08 12:54 ` Neil Horman
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=1273176614.2222.21.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=yoshfuji@linux-ipv6.org \
/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