v4.43.0

Features

• Shadowsocks Send Shadowsocks handshake with payload data if available (#1292 Thanks @nekohasekai)
• TFO Custom TCP Fast Open queue length support (#1293 Thanks @AkinoKaede)

Fixes

• Trojan fallback cannot get ALPN (#1286 Thanks @AkinoKaede)
• QueryStrategy ignored (#1285 Thanks @nekohasekai)
• UDP connection transport connection terminated unnecessarily (#1305 Thanks @Ovear)

Chores

• refactor: move from io/ioutil to io and os package (#1298 Thanks @Juneezee)
• Fix some tests to use udp.PickPort() (#1302 Thanks @yuhan6665 )
• Fix flaky TestVMessDynamicPort (#723) (#1289 Thanks @yuhan6665)

!!! Important Message !!!

V2Ray(V2Fly) will pre-release its next major version: V2Ray V5. In addition to functionality improvements, it will include a new configuration format and infrastructure changes that streamline the development of new protocols and functionalities.

The V4 version of the V2Ray will then enter maintenance mode. No additional features will be added by core developers, while contributors may still send pull requests for new features. It will receive bug fixes and security updates from core developers for a limited period until the full release of the V5 version. Contributors are encouraged to fork and base their changes from V5 version branch, instead of V4 version to reduce merge conflict. If you have already started the development of a change based on V4 version, you may send your pull request to V4 branch for a limited period. The core developers will cherry-pick that change into V5 version on your behave.

The pre-release version of V2Ray V5 may still contain bugs or inconsistencies. Some breaking updates to it are expected. You will need to change your configuration or codebase alongside us if you switch to V2Ray V5 now.

When V2Ray V5 pre-releases the master branch will switch to V5 version of the codebase, and the new V5 binary will be pre-released in the Github Release. They are not suitable for an automatic update from the V4 version.

Notice

Due to increase in size of the geoip.dat file recently, devices with insufficient ROM/RAM are experiencing difficulties in using V2Ray. The solution is as follows:

• For RAM insufficient devices: Enable the Geodata loader optimized for memory-constrained devices by setting the environment variable V2RAY_CONF_GEOLOADER to value memconservative. For more details, see documentation.
• For ROM insufficient devices:
  • Use the newly added GeoIP file geoip-only-cn-private.dat in the zip package or download it from release page, which only contains GeoIP list geoip:cn and geoip:private, or
  • Customize your own GeoIP file via project v2fly/geoip.