gccgo, remove flags
The project gets rid of
GOPATH mode entirely from now on. Use
go mod command as your first choice while developing.
For more information, visit:
0in V2Ray v4.28.0+
V2Fly’s signing infrastructure has been revised. You can from now on verify V2Fly’s release with the “Release” signed manifest file with v2ctl.
VMessAEAD has been updated to rely more on AEAD.
Outbound traffic accounting API. Thanks @yuhan6665
HTTP outbound can now handle HTTP2 over TLS, HTTP 1.1 over TLS in addition to HTTP 1.1 proxy traffic. Thanks @darhwa
ARM release will from now on have an explicit version in it. Thanks @rprx
V2Ray will from now on generate Windows 32 ARM binary release.
Minor code tidy up. Thanks Roger Shimizu.
Minor code tidy up. Thanks @agioi
Fix crash when the client supplied an invalid domain name to DoH. Thanks @DuckSoft
Further remove the identity leakage with TLS ClientHello from https://github.com/v2ray/v2ray-core/pull/2521 thank @darhwa
Fix UDP stability issue in Socks5 inbound, Shadowsocks inbound, and Dokodemo( TProxy ) inbound. This should alleviate unnecessary CPU, memory usage, and premature disconnection issue typically triggered by playing games, video conference, and Torrenting. See https://github.com/v2ray/v2ray-core/issues/2565 thank @JimHan75d8c5 @xiaokangwang and Other testers @1265578519 @zhj9709 @Kylejustknows etc
Added ARM v5 binary in the release. This should allow legacy ARM devices to run V2Ray correctly. See https://github.com/v2ray/v2ray-core/issues/2536
VMess's new header format experiment begins. You can now enable VMessAEAD to be better protected. Documents EN CH are updated. See extra-VMessAEADdoc.zip for a more detailed explanation available in both Chinese and English.
mKCP can now be encrypted to resist recognition, address issue mentioned in https://github.com/v2ray/v2ray-core/issues/2530 https://github.com/v2ray/v2ray-core/issues/2253 https://github.com/v2ray/v2ray-core/issues/2131. Documents EN CH are updated.
We are aware some anti-virus software detects V2Ray as malware, which it isn't, but we can't afford to pay the fee needed to make them not detect V2Ray as malware. Microsoft's AV detects V2Ray as "Trojan:Win32/Wacatac.C!ml" , "Program:Win32/Wacapew.C!ml" each time we release a new version, and I have to manually contact them each time to remove it from the malware database. If you have more information to report please leave them here. These AVs are known to generate false-positive results: "Microsoft", "McAfee", "Cylance", "Symantec", "F-Secure", "SecureAge APEX", "Cybereason", "Cynet", "MaxSecure", "F-Secure", "Avira", "AVAST", "AVG", "Rising"(瑞星).
Please refer to https://github.com/v2fly/v2ray-core/releases for further updates instead of the V2Ray release page. Currently, update in V2Fly will be mirrored to the V2Ray release page but this will NOT continue indefinitely.
This fix can significantly hindrance attack based on the weakness described. Only servers need to be updated to apply this emergency fix, it not expected for well-behaved clients to be influenced. A more permanent solution is underway.