相关问题
In V2RayN, when fetching a subscription (e.g., via URL), it only sends basic request data without any device-specific identifier. This limits integration with subscription providers that use HWID for device binding (common in panels like Remnawave). Users have to manually handle keys or face issues with multi-device limits.
描述你希望的解决方案
Implement optional HWID transmission in subscription requests, similar to Happ: Generate a unique HWID (e.g., based on CPU ID, motherboard serial, or a secure hash like in Happ). Append it to the subscription URL or headers (e.g., as a query param: ?hwid=xxxx or in User-Agent). Make it toggleable in settings (for privacy-conscious users). Ensure it's secure (hashed, not plain text) to avoid privacy risks. This could be added in the "Subscription" tab or as a global option.
描述你所考虑的替代方案
我确认已查询历史issues
相关问题
In V2RayN, when fetching a subscription (e.g., via URL), it only sends basic request data without any device-specific identifier. This limits integration with subscription providers that use HWID for device binding (common in panels like Remnawave). Users have to manually handle keys or face issues with multi-device limits.
描述你希望的解决方案
Implement optional HWID transmission in subscription requests, similar to Happ: Generate a unique HWID (e.g., based on CPU ID, motherboard serial, or a secure hash like in Happ). Append it to the subscription URL or headers (e.g., as a query param: ?hwid=xxxx or in User-Agent). Make it toggleable in settings (for privacy-conscious users). Ensure it's secure (hashed, not plain text) to avoid privacy risks. This could be added in the "Subscription" tab or as a global option.
描述你所考虑的替代方案
我确认已查询历史issues