Repository navigation
Follow-up through private security reporting channel #566
Description
I have removed the technical details from this public report so the finding can be triaged privately first.
I will follow up through the maintainer's preferred private security reporting channel once it is confirmed in #569, and coordinate any subsequent public issue or PR with the maintainer.
I am working toward a fix as @proletesseract.
Activity
[-]Disk logging does not follow configuration failures and live setting changes[/-][+]Follow-up through private security reporting channel[/+]