The parameters in the configuration file, in general, apply only to certificate operations. The openssl application does way more than certificate operations, and seeing a warning for a configuration file that has no impact on the operation being performed is annoying. Rather than completely remove the warning, I would instead suggest that the warning only be issued for certain commands that may use parameters from the configuration file.
-- -Todd Short // [email protected]<mailto:[email protected]> // “One if by land, two if by sea, three if by the Internet." On May 28, 2015, at 8:19 AM, Blumenthal, Uri - 0553 - MITLL <[email protected]<mailto:[email protected]>> wrote: If I want and expect openssl to use a config file, and it did not find it - it's darn useful for me to be informed of that fact by openssl. ----- Original Message ----- From: Rich Salz via RT [mailto:[email protected]] Sent: Wednesday, May 27, 2015 08:44 PM To: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> Subject: [openssl-dev] [openssl.org<http://openssl.org> #3876] [PATCH] Do not complain if config file not found Because it goes ahead and proceeds. Not it is explicit testing ENOTFOUND. It should either error+exit or not complain. I can be convinced the current behavior is useful. -- Rich Salz, OpenSSL dev team; [email protected]<mailto:[email protected]> _______________________________________________ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev _______________________________________________ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
