Félix Sipma writes:
> I do not see this bug anymore (no need to set
> "priority = SECURE256:!CTYPE-X.509:+CTYPE-OPENPGP:+SIGN-RSA-SHA224"
> in /etc/mandos/mandos.conf).
>
> So, this bug may be closed, at least on sid... But I would be nice to
> understand why it works now :-)
The source of these
I do not see this bug anymore (no need to set
"priority = SECURE256:!CTYPE-X.509:+CTYPE-OPENPGP:+SIGN-RSA-SHA224"
in /etc/mandos/mandos.conf).
So, this bug may be closed, at least on sid... But I would be nice to
understand why it works now :-)
signature.asc
Description: Digital signature
Teddy Hogeborn writes:
> Uncommenting the "priority" setting in mandos.conf and appending
> ":+SIGN-RSA-SHA224" makes it work; i.e. this line should be present in
> /etc/mandos.conf:
>
> priority = SECURE256:!CTYPE-X.509:+CTYPE-OPENPGP:+SIGN-RSA-SHA224
I meant, of course, /etc/mandos/mandos.conf
Uncommenting the "priority" setting in mandos.conf and appending
":+SIGN-RSA-SHA224" makes it work; i.e. this line should be present in
/etc/mandos.conf:
priority = SECURE256:!CTYPE-X.509:+CTYPE-OPENPGP:+SIGN-RSA-SHA224
I wish I knew why this works - I arrived at this by trial and error.
I'm susp
Package: mandos
Version: 1.5.5-1
Followup-For: Bug #702120
The same problem appeared here after upgrading from squeeze to wheezy... It
should have been a RC bug :-(.
-- System Information:
Debian Release: 7.0
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates')
Architectur
Package: mandos
Version: 1.6.0-1
Severity: grave
Justification: renders package unusable
Installing mandos ( from unstable or wheezy ) leads to a failing connection.
Setup: 2 new wheezy installs in a VM each on the same subnet.
1 VM client, 1 VM server.
Connection is established properly, bu
6 matches
Mail list logo
