Release demo mode marks the helper connected and enforcement on without applying it
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 54/100
Research direction
Read the startup paths in Sources/GUI/App/FreeSnitchApp.swift:113-135, 148-164, and 194-208, then trace the enforcement flag in Sources/GUI/ViewModels/AppState.swift:171-177. Check release startup with FREESNITCH_DEMO=1 and confirm the window does not report helper or enforcement as live when those services were skipped. Done when release startup cannot present fabricated helper and enforcement state.
Written by the indexing model from the issue text.
Description
I can select the demo startup path in a release build using its launch environment. FreeSnitchApp.swift:113 checks environment["FREESNITCH_DEMO"] == "1" without a debug guard and sets the helper state to connected. Lines 133-135 skip extension activation, and AppState.swift:175 sets enforcementEnabled = true while suppressing the helper request. This proves fabricated app state, not that an existing filter is stopped or that every readiness indicator reports protection. I have not checked the resulting release window on a Mac.
Steps
- Start the release app with FREESNITCH_DEMO=1 in its launch environment.
- Startup skips helper registration/connection and extension activation.
- The app marks the helper connected and sets the enforcement flag to true without applying enforcement.
Where
Sources/GUI/App/FreeSnitchApp.swift:113-135Sources/GUI/App/FreeSnitchApp.swift:148-164Sources/GUI/App/FreeSnitchApp.swift:194-208Sources/GUI/ViewModels/AppState.swift:171-177
Done when: Release startup cannot silently present fabricated helper and enforcement flags as live state.
I found this reading the code and haven't reproduced it on a signed build yet: the release app presentation with the demo environment needs checking.
- 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