Some more info on this.
I commented out the unlink statements so I could debug. The openssl verify command validates the cert fine using the same CA file and chain path as OpenCA uses.
I also compared the pkcs7 files that openca-sv uses. One file is extracted from the database and the other file is recalculated. Both files are exactly the same using binary diff.
So I am confused why the UI fails.
Dave
Sent from XFINITY Connect Mobile App
-----Original Message-----
From: blain...@gdls.com
To: he...@hlrs.de
Cc: openca-users@lists.sourceforge.net
Sent: 2014-09-05 09:41:30 GMT
Subject: Re: [Openca-Users] OpenCA 1.5.1 signature not valid
Hi Martin,
Although there are some cases of expired RA certificates, there are others were certs are signed by a valid RA certificate yet cannot be verified. See output from verification window below:
|
Based on your comments about hashes I did notice the hash values in the root chain directory were different between the old installation (using 0.9.8) and the new installation. I changed the Makefile to use subject_hash_old and rebuilt the chain. This only made matters worse. It was "unable to get issuer certificate". So I switched the hashes back.
If the hashes need to be changed anywhere else I am unaware of it.
Dave
------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/
_______________________________________________ Openca-Users mailing list Openca-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openca-users
------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/
_______________________________________________ Openca-Users mailing list Openca-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openca-users