Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add tests for plaintext leaking in logs

Open
#136 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
32/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
go

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.

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.

Dominant language
Go
Stars
18
Forks
12
Avg merge
1h 20m
Merged PRs (30d)
3

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from matrix-org/complement-crypto

All issues in matrix-org/complement-crypto

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.