Also using TinyCA2, creating certificates for servers with long hostnames (35 characters in my case), you encounter this bug. TinyCA2 tries to create a filename out of a Base64 hash of the CN (when it generates the CSR and the private key for the host).
Also using TinyCA2, creating certificates for servers with long hostnames (35 characters in my case), you encounter this bug. TinyCA2 tries to create a filename out of a Base64 hash of the CN (when it generates the CSR and the private key for the host).
DEBUG return: /usr/bin/openssl req -new -keyform PEM -outform PEM -passin env:SSLPASS -config /home/me/ .TinyCA/ CA/openssl. cnf -out /home/me/ .TinyCA/ CA/req/ Z2VvMDEubWFwcy5 kZXZibG4uZXVyb3 BlLm5va2lhLmNvb TpudW56aW8udmlz Y2lhbm9Abm9raWE uY29tOkxvY2F0aW 9uIFN5c3RlbSBFb mdpbmVlcnM6Tm9r aWEgU2VydmljZXM 6QmVybGluOkJlcm xpbjpERQ= =.pem -key /home/me/ .TinyCA/ CA/keys/ Z2VvMDEubWFwcy5 kZXZibG4uZXVyb3 BlLm5va2lhLmNvb TpudW56aW8udmlz Y2lhbm9Abm9raWE uY29tOkxvY2F0aW 9uIFN5c3RlbSBFb mdpbmVlcnM6Tm9r aWEgU2VydmljZXM 6QmVybGluOkJlcm xpbjpERQ= =.pem -sha1
Error opening Private Key /home/me/ .TinyCA/ CA/keys/ Z2VvMDEubWFwcy5 kZXZibG4uZXVyb3 BlLm5va2lhLmNvb TpudW56aW8udmlz Y2lhbm9Abm9raWE uY29tOkxvY2F0aW 9uIFN5c3RlbSBFb mdpbmVlcnM6Tm9r aWEgU2VydmljZXM 6QmVybGluOkJlcm xpbjpERQ= =.pem 02001024: system library:fopen:File name too long:bss_ file.c: 356:fopen( '/home/ me/.TinyCA/ CA/keys/ Z2VvMDEubWFwcy5 kZXZibG4uZXVyb3 BlLm5va2lhLmNvb TpudW56aW8udmlz Y2lhbm9Abm9raWE uY29tOkxvY2F0aW 9uIFN5c3RlbSBFb mdpbmVlcnM6Tm9r aWEgU2VydmljZXM 6QmVybGluOkJlcm xpbjpERQ= =.pem', 'r') 20074002: BIO routines: FILE_CTRL: system lib:bss_file.c:358:
6343:error:
6343:error:
unable to load Private Key