[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <482C8184.2030906@garzik.org>
Date: Thu, 15 May 2008 14:31:32 -0400
From: Jeff Garzik <jeff@...zik.org>
To: Rick Jones <rick.jones2@...com>
CC: "Brandeburg, Jesse" <jesse.brandeburg@...el.com>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Chris Peterson <cpeterso@...terso.com>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] drivers/net: remove network drivers' last few uses of
IRQF_SAMPLE_RANDOM
Rick Jones wrote:
> Is there nothing associated with the networking stack - NIC, driver,
> protocols, system calls which can be used as a source of entropy?
The issue is with being externally observable and controllable, or, with
some irq mitigation schemes, be made /too regular/.
Interrupts (or timed mitigation events) may be triggered by the outside
world, which makes it a very short path from remote attacker to local
kernel entropy pool.
Finally, with severe load, there are little or no interrupts thanks to
heavy mitigation, which means your entropy pool may be externally DoS'd.
Or at the very least, when your entropy needs to be INCREASED (due to
heavy workload due to heavy traffic), your incoming entropy DECREASES
due to decreased interrupts.
[I just realized that last one. Heck, I'm even convincing myself even
more its a bad idea]
Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists