Jeff Dike wrote:
> If nothing else works, I suppose a nasty workaround might be to
> replace /dev/random with dev/urandom, but that has security
> implications.
I am aware of the implications, but unfortunately it did
not help either.
# ls -l /dev/*random*
crw-rw-rw- 1 root root 1, 8 2008-08-05 17:41 /dev/oldrandom
lrwxrwxrwx 1 root root 7 2008-08-05 17:41 /dev/random -> urandom
crw-rw-rw- 1 root root 1, 9 2008-08-05 17:42 /dev/urandom
# grep random /var/log/auth.log
Aug 5 19:53:50 dirk sshd[3117]: fatal: Couldn't obtain random bytes (error
604389476)
# cat /proc/sys/kernel/random/entropy_avail
335
I am now talking to the host owner - he is running quite
a few UML guests, each in chroot environment, and one of the
problems is that his entropy gets sucked out...
Now he has replaced random with urandom in my chroot jail,
so the UML's random is his urandom. Let's see what happens...
--
Stano
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
User-mode-linux-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
