[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <482C8A99.80702@garzik.org>
Date: Thu, 15 May 2008 15:10:17 -0400
From: Jeff Garzik <jeff@...zik.org>
To: "Kok, Auke" <auke-jan.h.kok@...el.com>
CC: Alan Cox <alan@...rguk.ukuu.org.uk>,
"Brandeburg, Jesse" <jesse.brandeburg@...el.com>,
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
Kok, Auke wrote:
> Jeff Garzik wrote:
>> Alan Cox wrote:
>>>> In short, I agree with Alan's IRQF_SAMPLE_DUBIOUS, and know of Linux
>>>> customers who also want the same.
>>> They should be made to read the Debian ssh security report - three times
>>> and understand the same would apply to them if something did cause their
>>> network packet arrivals to be observed or non-random
>>>
>>> Far better would be to get your CPU guys to put an RNG back into the
>>> systems or on the CPU die ala VIA. Given I've even seen people using VIA
>>> boxes as a random number feeder (streaming random numbers over SSL) there
>>> is clearly a demand 8)
>> The Treacherous Platform Module includes an RNG.
>>
>> Someone (hi Jesse?) should implement support for TPM_GetRandom.
>
> Sounds like something he should neither use in the e1000 driver nor implement :)
>
> This would be an interesting thing to the generic rng support in linux though
That's what I meant. Support should be implemented in the appropriate
place in order to solve the problem Jesse's complaining about. That
appropriate place being drivers/char/hw_random/
Jeff
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists