fix(proxy): forward DNS for all non-denied domains, remove ChannelGateMiddleware#8
Merged
Merged
Conversation
…eMiddleware Two fixes: 1. DNS interceptor now only blocks domains with explicit deny rules. Previously, any domain not matching an allow rule got NXDOMAIN, silently preventing connections from reaching the SOCKS5 approval flow. Now DNS resolves for all domains, and policy enforcement (allow/ask/deny) happens at the SOCKS5 CONNECT level where the Telegram approval broker can prompt the user. 2. Removed ChannelGateMiddleware that blocked all /api/* routes when no HTTP channel was enabled. The API is now accessible whenever SLUICE_API_TOKEN is set, regardless of channel configuration. Bearer token auth is sufficient protection.
This was referenced Apr 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary