> Would people be ok with kernel auto-feeding for /dev/urandom only? I'veAndi, can you please clarify what you mean by "auto-feeding /dev/urandom only" and "only get blocking /dev/random with the user daemon"? Are you suggesting that the kernel provides /dev/urandom and a userspace daemon (e.g. EGD) provides /dev/random? Also, if crypto apps like ssh and openssl use on "insecure" /dev/urandom, then who actually relies on /dev/random? For comparison, FreeBSD does not even (AFAIK) have /dev/urandom. FreeBSD's /dev/random is nonblocking (like Linux's /dev/urandom) and includes network entropy. chris -- 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
| Mike Galbraith | Re: regression: CD burning (k3b) went broke |
| Andi Kleen | [PATCH] [3/22] x86_64: Kill temp boot pmds |
| Alan Cox | Re: [PATCH][RFC] 4K stacks default, not a debug thing any more...? |
| Greg Kroah-Hartman | [PATCH 004/196] Chinese: add translation of SubmittingPatches |
git: | |
| David Miller | [GIT]: Networking |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 05/37] dccp: Cleanup routines for feature negotiation |
| Brandeburg, Jesse | RE: [PATCH] e1000e: test MSI interrupts |
