The helper writes raw DNS names and paths as public system-log text
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 57/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- macos, swift
- Domain
- observability, security
Research direction
Read Sources/Shared/Logger.swift:12-14 and inspect the listed logging calls in HelperService.swift and BundlePresenceWatcher.swift to see which values are written as public text. Start by checking the project’s logging and diagnostic disclosure conventions. Done means failure context remains useful while DNS names, paths, endpoints, and configured URLs are private or omitted unless the user opts in.
Written by the indexing model from the issue text.
Description
Each PSLog function formats the whole message as %{public}@, so interpolated values are not privacy-redacted. The helper includes queried hostnames, resolver URLs, IPs, bundle paths, and filesystem paths in these messages; for example, line 99 logs domain and line 565 logs the rejected stored URL. Apple documents .public values as visible in unified logs (OSLogPrivacy.public).
Steps
- A DNS ask for an internal or personal hostname cannot be delivered to the GUI, so HelperService logs the domain.
- The log is inspected by a local account or support collector with unified-log access, or included in a diagnostic capture the user shares.
- Because the message is public rather than redacted, that reader learns the hostname and any other raw values in the captured messages.
Where
Sources/Shared/Logger.swift:12-14Sources/Helper/HelperService.swift:99-111Sources/Helper/HelperService.swift:159Sources/Helper/HelperService.swift:559-570Sources/Helper/BundlePresenceWatcher.swift:287-288
Done when: System logs retain useful failure context while DNS names, user paths, endpoint values and configured URLs are private or omitted unless a user explicitly opts into diagnostic disclosure.
I found this reading the code.
- Dominant language
- Swift
- Stars
- 49
- Forks
- 5
- Avg merge
- 16h 48m
- Merged PRs (30d)
- 82
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 isaaclins/freesnitch
-
area:cli documentation good first issue priority:low
Difficulty 1/5 Under an hour Newbie friendliness 94/100
isaaclins/freesnitch#430 ·
Maintainers usually reply within 1 day
-
area:gui bug priority:low status:queued
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
isaaclins/freesnitch#428 ·
Maintainers usually reply within 1 day
-
area:shared bug priority:high status:queued type:correctness
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
isaaclins/freesnitch#284 ·
Maintainers usually reply within 1 day
-
area:helper bug priority:medium status:queued type:diagnostics
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
isaaclins/freesnitch#282 ·
Maintainers usually reply within 1 day
-
area:gui bug priority:low status:queued type:correctness
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
isaaclins/freesnitch#281 ·
Maintainers usually reply within 1 day
All issues in isaaclins/freesnitch
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
good first issue help wanted testing
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
MasterJ93/ATProtoKit#354 ·
-
enhancement help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
heysidhant/appvanish#4 ·
-
bug priority:low status:queued
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day