Right now, debug mode will output a lot of private data (e.g. domains being looked up). We should clearly warn the user of this if debug mode is enabled (both by outputting a warning, and in end user documentation). We should also audit the code to make sure that no private data is leaked outside of debug mode (I wouldn't be surprised at all if we fail this test right now).
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/9069478-debug-output-privacy?utm_campaign=plugin&utm_content=tracker%2F435873&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F435873&utm_medium=issues&utm_source=github).
Right now, debug mode will output a lot of private data (e.g. domains being looked up). We should clearly warn the user of this if debug mode is enabled (both by outputting a warning, and in end user documentation). We should also audit the code to make sure that no private data is leaked outside of debug mode (I wouldn't be surprised at all if we fail this test right now).