News for hackers. Stuff that matters.
Re:Log4Shell update: second Log4j vulnerability published by kubanczyk on Wednesday December 15, 2021 @03:57AM (#29563541)
Usually there is no universal way to find the latest version of internal documentation across teams, hence updating such documentation is barely worth the time. People notice the fact.
Re:Log4Shell update: second Log4j vulnerability published by nefitty on Wednesday December 15, 2021 @04:52AM (#29563853)
In your mind, do hosted wikis and KBs like Stack Exchange, Wikimedia or Confluence address the discovery problem? If not, is there anything close?
Re:Log4Shell update: second Log4j vulnerability published by nitrogen on Wednesday December 15, 2021 @01:38PM (#29569914)
Not the OP, but I am a fan of leaving breadcrumbs everywhere. That is, every bit of documentation should point to other bits of documentation. Code comments point to the corporate wiki and vice versa, commit messages point to issues, issues refer to commit hashes, log messages might say who wrote a service, bespoke server and container images could have a README in /, internal DNS can have text records, etc.

We have to accept that we will sometimes play digital archaeologist. That's a good thing! It means that the technology we're studying was successful. So given that, it's better to have out of date documentation than zero documentation, so that we can pick up the trail somewhere.