Description of problem: openssl returns success code on bad arguments Also happens on mga4. Version-Release number of selected component (if applicable): How reproducible: ALways Steps to Reproduce: openssl -cert no.way xx yy echo $? Note return status is 0 (success) Reproducible: Steps to Reproduce:
Is this bug specific to Mageia, or an upstream bug? If the latter, please look for an existing bug open upstream, or open one, and add the link here. Also add the UPSTREAM keyword.
Summary: 5: openssl returns success code on bad arguments => openssl returns success code on bad argumentsWhiteboard: (none) => MGA5TOO
Keywords: (none) => NEEDINFO
(In reply to Samuel VERSCHELDE from comment #1) > Is this bug specific to Mageia, or an upstream bug? Going to guess upstream. :( > If the latter, please look for an existing bug open upstream, or > open one, If you were to look in file:///usr/share/doc/openssl/README a bug report requires a lot of information I do not have. > and add the link here. Also add the UPSTREAM keyword. After rooting around, I finally find http://rt.openssl.org/NoAuth/Buglist.html and a search for return+code get the following bug reports that indicate to me that maintainers have no great interest in fixing return code problems. Trimmed down snippet of my search results: 2877 rand does not check write(2) return code new 3 years ago 2919 Incorrect return code and printing of modulus in dsa module new 3 years ago 3092 Verify return code: 20 (unable to get local issuer certificate) 2 years ago 3787 [PATCH] Update the return value documentation for various EVP_* functions to match the code. new 2 months ago Obviously Mageia people are not going to fix the return status problems, so I'll go ahead and mark it resolved wontfix.
Keywords: NEEDINFO => (none)Status: NEW => RESOLVEDResolution: (none) => WONTFIX