You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the feature you'd like to see in EvoSC
There should be some better control over the logging output in form of logging levels. This is very useful when setting up servers in production, testing, and development.
There are some security implications as well with the current logging system. Taking this screenshot as an example:
Here we see the server credentials being written straight into the logs when an error occurred. This can be very bad as malicious users could potentially obtain full control over the server from a lower privilege level. By having logging level support, stack traces like these can be disabled in production environments.
I suggest the following logging levels:
Fatal: For errors that can result in a crash or a component of the controller no longer working properly.
Error: Anything that failed or errored, but does not necessarily result in a crash or non-working components and is recoverable.
Warning: For anything that was unexpected with minor disturbances to the program flow.
Info: Generic message indicating a change of or current state of the controller.
Debug: A higher level of verbosity of info. Can include stack traces and may have some sensitive information.
Trace: A higher level of verbosity of Debug and can contain messages with internal object values, including any level of sensitive information.
A "trace" level, can be added, but it's not really necessary, but it can be set to enable the highest verbosity level (-vvv).
The logging level should be configurable in a config file.
Feel free to comment your opinion or come with suggestions that can improve this idea.
The text was updated successfully, but these errors were encountered:
Describe the feature you'd like to see in EvoSC
There should be some better control over the logging output in form of logging levels. This is very useful when setting up servers in production, testing, and development.
There are some security implications as well with the current logging system. Taking this screenshot as an example:
Here we see the server credentials being written straight into the logs when an error occurred. This can be very bad as malicious users could potentially obtain full control over the server from a lower privilege level. By having logging level support, stack traces like these can be disabled in production environments.
I suggest the following logging levels:
A "trace" level, can be added, but it's not really necessary, but it can be set to enable the highest verbosity level (-vvv).
The logging level should be configurable in a config file.
Feel free to comment your opinion or come with suggestions that can improve this idea.
The text was updated successfully, but these errors were encountered: