Potential Information Leakage
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
Research direction
Start in tabpy/utils/tabpy_user.py at the linked line where the user name and password are sent to the logger. Reproduce the add-user flow, then verify that the resulting log output no longer exposes the password while retaining useful context.
Written by the indexing model from the issue text.
Description
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 614
- Avg merge
- 2d 27m
- Merged PRs (30d)
- 1
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.
More from tableau/TabPy
-
question
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
question
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
question
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
-
question
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
zostera/django-bootstrap4#894 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
use-agent-os/agent-os#3276 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
zephyrproject-rtos/zephyr#119726 ·
-
area/auth bug comp/agent P3 platform/discord type/security
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#117848 ·