4 ms·
We literally just saw a case[0] where an application (iterm2) mistakenly left verbose logging on in a component of a production build and logged sensitive conso
by mvdtnz 2y ago
We literally just saw a case[0] where an application (iterm2) mistakenly left verbose logging on in a component of a production build and logged sensitive console contents to connected hosts.
Are you diligent enough to remove your sensitive logging/printf statements EVERY time, for the rest of your career? Or should you make a habit of doing things properly from day one?
0 https://news.ycombinator.com/item?id=42579472 https://news.ycombinator.com/item?id=42579472
- jaredsohn 2y ago>Are you diligent enough to remove your sensitive logging/printf statements EVERY time Yes, when a linter is set up that fails when printf debugging is found