Export functionality to exclude sensitive properties
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
The issue names no files, tests, or entry points. Start by locating the existing configuration serialization or export code, then determine how sensitive properties would be identified. Done means a separate configuration export replaces those values so users can share it without exposing passwords or other sensitive data.
Written by the indexing model from the issue text.
Description
As seen in AuthMe, sometimes users need to report their configuration files but such files might include sensitive information like passwords we want to make sure users don't expose. Potentially could be solved by offering some sort of export functionality to save to a separate file that will replace data from sensitive properties (as indicated with an annotation?)
Relates to https://github.com/AuthMe/AuthMeReloaded/issues/1991
- Dominant language
- Java
- Stars
- 44
- Forks
- 21
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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 AuthMe/ConfigMe
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
-
architecture
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
PropertyValue: Specify if value is default or notMay be free again @ljacqu claimed this 77 days ago, and no pull request is open. Open
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
grimmory-tools/grimmory#2850 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
aoqia194/leaf-loader#19 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
apache/streampark#4521 ·
-
Update license yearOpen0 - Backlog 1 - Ready documentation good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100