Your message dated Fri, 1 Dec 2006 14:27:46 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#398789: fails to install in a vserver - PRNG is not seeded has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---package: ssh-krb5 version: 3.8.1p1-10 severity: serious Hi, Setting up ssh-krb5 (3.8.1p1-10) ... Creating SSH2 RSA key; this may take some time ...PRNG is not seeded dpkg: error processing ssh-krb5 (--configure): subprocess post-installation script returned error exit status 255 <h01ger> hi. uninstallable packages are RC and not important, or? #385950 <aba> ah, fails to install is RC <Sesse> hmf, we need a java person to take #397567 <h01ger> and fails to install in a vserver? (ssh-krb5: PRNG is not seeded) - no bug filed yet.. <Sesse> h01ger: in a vserver is a bit of an odd use case <aba> Sesse: not really <aba> h01ger: I'm not going to cluebat you for filing it as serious ... regards, Holger
pgpWtOzV6Sq5E.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---* Holger Levsen ([EMAIL PROTECTED]) [061201 14:08]: > lambda:/# ssh-keygen -t rsa > PRNG is not seeded > lambda:/# > > open("/dev/urandom", O_RDONLY|O_NONBLOCK|O_NOCTTY) = -1 ENOENT (No such file > or directory) > open("/dev/random", O_RDONLY|O_NONBLOCK|O_NOCTTY) = -1 ENOENT (No such file > or directory) > open("/dev/srandom", O_RDONLY|O_NONBLOCK|O_NOCTTY) = -1 ENOENT (No such file > or directory) > connect(3, {sa_family=AF_FILE, path="/var/run/egd-pool"}, 19) = -1 ENOENT (No > such file or directory) > connect(3, {sa_family=AF_FILE, path="/dev/egd-pool"}, 15) = -1 ENOENT (No > such file or directory) > connect(3, {sa_family=AF_FILE, path="/etc/egd-pool"}, 15) = -1 ENOENT (No > such file or directory) > connect(3, {sa_family=AF_FILE, path="/etc/entropy"}, 14) = -1 ENOENT (No such > file or directory) You can see that all ways how (pseudo)-entropy can be taken are locked somehow. I recommend to have /dev/*random available also inside a vserver, otherwise lots of applications are hitten bad. Cheers, Andi -- http://home.arcor.de/andreas-barth/
--- End Message ---
