matrix-org / matrix-org/complement-crypto
Add tests for plaintext leaking in logs
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 18
- Forks
- 12
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 6
Description
It's very important we don't leak plaintext messages in logs. We should be able to test that stdout/log files do not contain certain sentinel strings. This may require some kind "please enable verbose logging" option in the API.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by tracing the API's logging and stdout paths, then determine how verbose logging should be enabled. Done means tests verify that stdout and log files do not contain the chosen plaintext sentinel strings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, security, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100