Re: Feeding /dev/random with /dev/urandom
From: Bill Unruh (unruh_at_string.physics.ubc.ca)
Date: 04/28/04
- Next message: erm67: "Re: Feeding /dev/random with /dev/urandom"
- Previous message: Jim Hatfield: "Re: sFTP compared with FTP via VPN"
- In reply to: erm67: "Feeding /dev/random with /dev/urandom"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 28 Apr 2004 21:17:46 +0000 (UTC)
ermscag@tin.it (erm67) writes:
]The latest linux kernel features a blocking /dev/random device, that
]is it will block when the available entropy is not sufficient. I found
]that some motherboards has a hw randomness generator and that it can
]be used, with rngd from http://sourceforge.net/projects/gkernel/ to
]feed /dev/random so that its entropy pools are always ready.
]My motherboard doesn't have this device and besides is very slow thus
]/dev/random often blocks.
]The 'solution' I found is to instruct rngd to read from /dev/urandom
](non blocking) and to feed /dev/random.
]Of course this seems quite silly even to me :-) but now
]/proc/sys/kernel/random/entropy_avail always reports that entropy is
]available and all apps reading /dev/random no longer blocks.
]The question the random number from /dev/random are still 'good' is
]using this method?
No.
/dev/urandom does not block by feeding your "random" data which is not
really random.
- Next message: erm67: "Re: Feeding /dev/random with /dev/urandom"
- Previous message: Jim Hatfield: "Re: sFTP compared with FTP via VPN"
- In reply to: erm67: "Feeding /dev/random with /dev/urandom"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
