securedrop-client
securedrop-client copied to clipboard
Published
20 hours ago •
freedomofpress
freedomofpress
log proxy events to syslog
Description
The Python securedrop-proxy responds to the caller exclusively on stdout, so it can use standard Python logging.
The Rust securedrop-proxy in #1718 responds with a mix of stdout and stderr, so it's silent. In testing, this makes it difficult to tell whether it (or some other proxy instance on the machine...) is handling a given request.
It would be nice to log proxy events to syslog just for testing purposes.
How will this impact SecureDrop users?
No user-facing changes.
How would this affect the SecureDrop Workstation threat model?
No threat-model implications: the current proxy implementation already has this behavior.
User Stories
As a developer, I want to be able to watch a securedrop-proxy instance and see that it's handling requests.
