News for hackers. Stuff that matters.
Re:Logs were our lifeblood, now they're our liability by ehsankia on Tuesday October 08, 2019 @05:23PM (#21197417)
At least one? Almost every one of the recent "plaintext password" headlines, of which there has been half a dozen or more, were due to that. And I'm sure there are many more cases happening right now without being noticed. It definitely is big issue.

And no, I don't think in most cases it's forgetting to remove the `console.log(req.body.password)`, but rather having a much wider `console.log(req)` which you didn't realize contains (or could in some other code path contain) a password. Or some log statement much deeper, 2-3 layers of abstractions away, logging some struct passing through the system, which happens to contain PII.

It definitely isn't a trivial issue with a simple solution, as some people commenting on such headlines seem to imply.

Re:Logs were our lifeblood, now they're our liability by ikiris on Wednesday October 09, 2019 @05:02AM (#21201369)
Its not that hard when you taint structs with PII, so that the log library faults if it tries to log it.
Re:Logs were our lifeblood, now they're our liability by zbentley on Wednesday October 09, 2019 @08:38AM (#21202550)
Ah yes, just handle tainting/laundering all data that flows into a system which is hooked up to thousands or hundreds of thousands of external data sources. Not that hard at all.

/s

Re:Logs were our lifeblood, now they're our liability by ikiris on Wednesday October 09, 2019 @07:46PM (#21209436)
So your alternative is... do nothing?
Re:Logs were our lifeblood, now they're our liability by ehsankia on Wednesday October 09, 2019 @08:33PM (#21209721)
Of course if your whole system is written with this in mind, it's doable. But many code bases are huge and fixing them isn't trivial.