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
Sensitive data can be printed by exposing all of the locals.
I've encountered one with using psycopg2. It stores database connection strings, and is exposed when there is an uncaught exception.
Proposed Resolution
Allow dict traceback or traceback.SHOW_LOCALS to be configured (currently it is hardcoded)
The text was updated successfully, but these errors were encountered:
Are you using structlog.processors.dict_tracebacks()?
This is just a shortcut for ExceptionRenderer(ExceptionDictTransformer()) which has a show_locals argument.
If secrets are wrapped with pydantic.Secret() or typed_settings.Secret(), they will not leak. But I think very few people actually to this and for external libs, you can't control this behavior.
So maybe changing the default of SHOW_LOCALS to False might be a good idea.
Sensitive data can be printed by exposing all of the locals.
I've encountered one with using psycopg2. It stores database connection strings, and is exposed when there is an uncaught exception.
Proposed Resolution
Allow dict traceback or traceback.SHOW_LOCALS to be configured (currently it is hardcoded)
The text was updated successfully, but these errors were encountered: