Fixed in the 1.0.2 branch. The master branch has had tremendous changes around
command line parsing and error reporting that the bug most likely disappeared
automatically.
Closing ticket
Cheers,
Richard
On Wed Mar 11 14:28:50 2009, vladimir.ko...@sun.com wrote:
>
> Hello,
>
> In case the openssl verify command is not able to process input file, it
> reports the usage even if the usage is perfectly okay:
>
> $ openssl verify -CAfile /local/Saved/SMI_SSL_CA-chain.pem cert.cer
> Error loading file /local/Saved/SMI_SSL_CA-chain.pem
> usage: verify [-verbose] [-CApath path] [-CAfile file] [-purpose
> purpose] [-crl_check] [-engine e] cert1 cert2 ...
> recognized usages:
> sslclient SSL client
> sslserver SSL server
> nssslserver Netscape SSL server
> smimesign S/MIME signing
> smimeencrypt S/MIME encryption
> crlsign CRL signing
> any Any Purpose
> ocsphelper OCSP helper
> $
>
>
> This is because of the following code in verify.c:
>
>
> if (CAfile) {
> i=X509_LOOKUP_load_file(lookup,CAfile,X509_FILETYPE_PEM);
> if(!i) {
> BIO_printf(bio_err, "Error loading file %s\n", CAfile);
> ERR_print_errors(bio_err);
> goto end;
> }
>
> The goto jumps to the code which prints the usage. Similarly for other
> input files.
>
> Also, it does not report what went wrong with the input file.
>
>
> v.
--
Richard Levitte
levi...@openssl.org
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=1866
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
