Investigating what we're filtering to Sentry
Open
Nobody has claimed this yet.
needs investigation
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
Description:
While reviewing Sentry alerts, we discovered that a user’s password is being exposed in the alert description. This issue is to investigate what we're exposing to Sentry.
https://openfn.sentry.io/issues/6793756076/events/1317cbcc35f348bea0704173ca939a56/
Contributor guide
No contributing guide indexed for this repository
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
Start with the linked Sentry issue and event, including the attached image, to identify what data appears in the alert description. Trace that data back through the application and document the filtering boundary. Done means the investigation identifies the exposure path and defines what sensitive data must not reach Sentry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100