-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 C. Dominik Bódi <dominik.b...@gmx.de> writes:
> After having enabled the debug mode via plugin-runner.conf as you > suggested. The "fatal" error occurs immediately after the first > debug messages, which is: > "Initializing GNUTLS" - From mandos-client.c: if(debug){ fprintf(stderr, "Initializing GnuTLS\n"); } ret = gnutls_global_init(); So the problem is definitely reported by GnuTLS (or libgcrypt). > Then I booted the kernel with the break option and ran "sh > scripts/init- premount/udev". Right, I forgot you need to run that too; sorry. > Indeed, it seems that both /dev/random and urandom are readable only > by user and group, respectively. I was hoping for it to be just a missing module to load, but no such luck, I guess. What were the exact permissions and ownerships? "crw-rw---- root root"? That would be very strange. I'll have to wait until tomorrow (when I should have access to a sid machine) to check which of the many changes from lenny to sid could cause it. On the bright side, we seem to have found the actual cause of the problem; we just need to get udev to create the devices with the proper permissions. /Teddy Hogeborn - -- The Mandos Project http://www.fukt.bsnet.se/mandos -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFKyPBEOWBmT5XqI90RAj0ZAJ4zYgbOjEGAC3yCGX0wHv1z0WBxkwCdEmHB +ruOGs6j2NdDLNr+vyrYAGo= =bUBW -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org