package mandos-client
retitle 549585 udev: creates /dev/{u,}random with too strict permissions
summary 549585 20
tags 549585 patch
reassign 549585 udev 146-3
package udev
affects 549585 mandos-client
thanks
Teddy Hogeborn te...@fukt.bsnet.se writes:
Indeed, it seems that both /dev/random and
Package: mandos-client
Version: 1.0.12-1
Severity: grave
Justification: renders package unusable
After installing mandos I tested my configuration as described in
README.Debian. That worked successfully. However, booting a
mandos-enabled kernel, mandos will not run. The cryptsetup password
prompt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
C. Dominik Bodi dominik.b...@gmx.de writes:
After installing mandos [...], booting a mandos-enabled kernel,
mandos will not run. The cryptsetup password prompt appears and I
have to type in the crypt volume's password manually to make the
system
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
C. Dominik Bodi dominik.b...@gmx.de writes:
After installing mandos [...], booting a mandos-enabled kernel,
mandos will not run. The cryptsetup password prompt appears and I
have to type in the crypt volume's password manually to make the
system
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
Then I booted the kernel with the break option and ran sh scripts/init-
premount/udev. Indeed, it seems that both
-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:
6 matches
Mail list logo
