rzo1 opened a new pull request, #46: URL: https://github.com/apache/stormcrawler-site/pull/46
The security model page names a class of defect the project treats as a security problem, but stops there. It does not say what follows from that, so there is nothing to triage a report against. This adds the missing half: * The shipped configuration is a starting point, not a secured deployment. StormCrawler is a library and the operator assembles the topology, so a weakness reachable because a control the page documents was not configured is a weak default. We improve the default and treat the change as hardening. * A control an operator did configure being defeated, or a configured secret being disclosed in a way the page does not describe, is a vulnerability. * An advisory follows when operators must act beyond taking the next release: change a configuration, inspect or repair stored data, or rotate a credential. Where the fix is enough on its own, it ships in a normal release and the release notes carry any operator-visible change. It also states that log output is not a confidentiality boundary, because DEBUG logging on the protocol implementations can write configured credentials to the logs. That is worth saying on its own. The boundary sentence under "Crawled Content Is Untrusted by Design" now says such defects are fixed first and points at the Advisories and Hardening section for whether an advisory follows, rather than reading as though the two are the same question. One paragraph replaced, three added, no other change. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
