Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debug message inconvenience #17

Open
Javex opened this issue Sep 27, 2012 · 1 comment
Open

Debug message inconvenience #17

Javex opened this issue Sep 27, 2012 · 1 comment

Comments

@Javex
Copy link

Javex commented Sep 27, 2012

When checking if an engine is statically compiled in OpenSSL, the output in case of failure is sent to STDERR. Therefore it is not captured but directly sent to the logfile and instead of a message like

[debug] Output is:
[...]

it looks like this:

[...]
[debug] Output is:

To fix this, STDERR needs to be captured or the messages need to be altered so it lookes correct. This really is a minor thing that just looks ugly.

Also, if CertNanny is not run in debug mode, then the output will be in the log file with no explanation whatsoever (which could lead to thinking this was an error, not expected behavior).

@Javex Javex closed this as completed Sep 27, 2012
@Javex Javex reopened this Sep 27, 2012
@aleibl
Copy link

aleibl commented Dec 18, 2013

Hi Florian,

Can you point me to the module and function where this check is performed?

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants