Hello,
> > I think that this returns proper return code, for example
> > (some prepared errors):
>
> I'll have to confirm, but this did not appear to be the case if the tool
> failed to sign a csr due to a preexisting CN already issued in a cert. I
> found just a size-zero file created.
Maybe good and acceptable solution to this problem will be
just always checking newly created certificate,
for example with command:
$ openssl verify -CAfile cacert.pem new_cert.pem
This should give you information on generated certificate status
independently from "openssl" return code, no space on disk error,
permission problems or other openssl/system errors.
Best regards,
--
Marek Marcola <[EMAIL PROTECTED]>
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager [EMAIL PROTECTED]
