Use /dev/urandom (which is non-blocking) instead of /dev/random (which
authorgerald <gerald@f5534014-38df-0310-8fa8-9805f1628bb7>
Wed, 6 Jan 2010 17:18:57 +0000 (17:18 +0000)
committergerald <gerald@f5534014-38df-0310-8fa8-9805f1628bb7>
Wed, 6 Jan 2010 17:18:57 +0000 (17:18 +0000)
commitf4dcae9888f48b4cea58c2bbc3479c818521f1f6
treef374edf04c5e6837930ed56032f29e19c1fdc044
parentebd7a92ffa1566286c8fa96da7a82fd3865c5d33
Use /dev/urandom (which is non-blocking) instead of /dev/random (which
can block forever) for our seed. This fixes a problem with our new Linux
build slave, which is running Linux 2.6 as a VM guest, and which was
timing out waiting for entropy.

Add a comment about using CryptGenRandom on Windows.

git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@31456 f5534014-38df-0310-8fa8-9805f1628bb7
randpkt.c