feat(proxy): JWT-preserving OAuth phantoms and DNS-based hostname recovery#3
Merged
nnemirovsky merged 1 commit intomainfrom Apr 7, 2026
Merged
Conversation
…overy Two features: 1. OAuth phantom tokens now preserve JWT structure. When the real access token is a JWT, the phantom keeps the header and payload (so clients can extract claims like accountId) but re-signs with sluice's own HMAC key. Non-JWT tokens fall back to deterministic SLUICE_PHANTOM strings. 2. DNS reverse cache recovers hostnames from IP-only SOCKS5 CONNECT requests. The DNS interceptor populates an IP->hostname cache from A/AAAA response records. The SOCKS5 handler uses this cache so Telegram approval messages show hostnames and hostname-based policy rules match correctly.
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