Johnny Gonzalez wrote:
CRIN: TMS8hU+b8oPhoYS55b/NaQ
How do you get this CRIN? Via encrypted email?
HASHED CRIN (openssl dgst -sha1 < Proyectos/SEMC/OpenCA/Vars/ProjectVars/CRIN11): 801ab1fa070f30ca4ca57fa8e47d306eaf40f284
I get the same.
PIN in db: 5e86d229d29e4f856f9b798cad5fe007808c6afc
I cannot get this hash from OpenSSL neither with 1111111111 nor with TMS... I also tried it with trailing newline and without.
PIN in clear text: 1111111111 (1 10 times)
1. What does the value be of USE_REQUEST_PIN in ca.conf? 2. PIN in the header of the request is the sha1 hash of the PIN. 3. PIN in the header of the cert is the sha1 hash of the CRIN. 4. If USE_REQUEST_PIN=YES then the two PINs in the headers are identical.
as you can see, nothing is similar here.
I don't think so.
Is there any openssl command you use to create the CRIN? or how is it created?
openssl rand -base64 1234 Michael -- _______________________________________________________________ Michael Bell Humboldt-Universitaet zu Berlin Tel.: +49 (0)30-2093 2482 ZE Computer- und Medienservice Fax: +49 (0)30-2093 2704 Unter den Linden 6 [EMAIL PROTECTED] D-10099 Berlin _______________________________________________________________
smime.p7s
Description: S/MIME Cryptographic Signature
