On Sat, Oct 06, 2001, David Brownell <[EMAIL PROTECTED]> wrote:
> > > AFAICT, all we need to do is add SA_SAMPLE_RANDOM to the request_irq call
> > > flags in the host controllers.
> >
> > I think most controllers interrupt every frame.
>
> UHCI sends a more regular stream of interrupts, since i
> > AFAICT, all we need to do is add SA_SAMPLE_RANDOM to the request_irq call
> > flags in the host controllers.
>
> I think most controllers interrupt every frame.
UHCI sends a more regular stream of interrupts, since it needs the
software to tend things rather often. OHCI and EHCI tend to use
> I am not saying that USB interrupts are necessarily a good source of
> entropy. But if you are using purely USB keyboard and mouse, then it might
> be the best source of entropy available.
No. Keyboard and mouse already add entropy. If you take anything else there's
a theoretical risk of someo
Pete Zaitcev wrote:
>
> > AFAICT, all we need to do is add SA_SAMPLE_RANDOM to the request_irq call
> > flags in the host controllers.
> >
> > Thoughts?
> >
> > Brad
>
> I think most controllers interrupt every frame.
> That would be a very poor source of entropy.
Assuming that /proc/interrupts
> AFAICT, all we need to do is add SA_SAMPLE_RANDOM to the request_irq call
> flags in the host controllers.
>
> Thoughts?
>
> Brad
I think most controllers interrupt every frame.
That would be a very poor source of entropy.
-- Pete
___
[EMAIL PROTE
After looking at Robert Love's patches for net devices contributing to the
entropy pool, it occurred to me that perhaps USB controllers should also
contribute (possibly on a config variable).
AFAICT, all we need to do is add SA_SAMPLE_RANDOM to the request_irq call
flags in the host controllers.
