fix(subscription): recognize InHive via is_v2ray (base64 links) to preserve kcp - #31
Open
twilgate wants to merge 2 commits into
Open
fix(subscription): recognize InHive via is_v2ray (base64 links) to preserve kcp#31twilgate wants to merge 2 commits into
twilgate wants to merge 2 commits into
Conversation
InHive (https://inhive.ru) is a public sing-box-based VPN client (github.com/TwilgateLabs: inhive-android, inhive-windows; iOS soon), UA "InHive/<ver> (<platform>; <hwid>)", core supports hysteria2/TUIC/Reality. Add the InHive token to both sing-box UA regexes (hutils/flask.py is_singbox flag + panel/user/user.py endpoint selection) so its UA is served the sing-box config instead of falling through to v2ray/base64. Co-Authored-By: Claude <noreply@anthropic.com>
The sing-box branch (to_singbox) drops kcp; the base64 links branch (to_link) carries the full protocol set including kcp. Move InHive from is_singbox to is_v2ray so its clients receive every configured protocol. Co-Authored-By: Claude <noreply@anthropic.com>
twilgate
changed the title
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.
Supersedes the original approach in this PR. Instead of adding InHive to the sing-box User-Agent group, this routes it to the base64 share-links group (
is_v2ray).Why the change from sing-box to base64 links
InHive is a universal client (sing-box + Xray parity) that ingests base64 share-links natively. The sing-box branch (
hutils/proxy/singbox.py) drops kcp —if proxy['l3'] == "kcp": return {... "msg": "does not support kcp" ...}. The base64 branch (links_imp→make_v2ray_configs→to_link) emits every configured proxy including kcp, so it's the only branch that delivers the full set. Routing InHive through sing-box would silently strip kcp from its users.InHive also isn't affected by the xray-json branch (which drops hysteria2/tuic), since that only fires for v2rayNG≥1.8.17 / Streisand — so it lands cleanly on the base64 links branch.
Changes
hiddifypanel/hutils/flask.py: remove InHive fromis_singbox, add tois_v2ray.hiddifypanel/panel/user/user.py: mirror the same in the routing branch.On safety: InHive uses per-install localhost auth (no open unauthenticated local proxy), so serving it the full config set carries no additional exposure. UA format:
InHive/<ver> (<platform>; <hwid>). Releases: github.com/TwilgateLabs.