> In short, I agree with Alan's IRQF_SAMPLE_DUBIOUS, and know of LinuxThey 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) Alan -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Arjan van de Ven | [Announce] Development release 0.1 of the LatencyTOP tool |
| Andrew Morton | -mm merge plans for 2.6.23 |
| Greg Kroah-Hartman | [PATCH 020/196] IDE: Convert from class_device to device for ide-tape |
git: | |
| Tantilov, Emil S | RE: [PATCH] net: sk_alloc() should not blindly overwrite memory |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
