The attached patch resolves the issue when creating a sub-ca. The
original patch was sent to me by Cédric Dufour
(cedric.duf...@ced-network.net). I have recreated the patch and added
it to my post.
On 14-11-14 5:07 PM, Thorsten Alteholz wrote:
Hi,
I am afraid the patches are not complete.
I can create a CA and the signatureAlgorithm says sha512 .
If I create a Sub-CA, the signatureAlgorithm says sha1 despite
selecting sha512 here as well.
Thorsten
--
Bill Thorsteinson
SysteMajik Consulting
diff --git a/CA.pm b/CA.pm
index 7e7fba6..479ca30 100644
--- a/CA.pm
+++ b/CA.pm
@@ -1062,6 +1062,7 @@ sub create_ca {
'outdir' => $self->{$ca}->{'dir'}."/newcerts/",
'keyfile' => $self->{$ca}->{'dir'}."/cacert.key",
'cacertfile' => $self->{$ca}->{'dir'}."/cacert.pem",
+ 'digest' => $opts->{'digest'},
'pass' => $opts->{'passwd'},
'days' => $opts->{'days'},
'parentpw' => $opts->{'parentpw'},
