Bump github.com/v2fly/v2ray-core/v4 from 4.38.0 to 4.38.2

[dependabot-preview]

⚠️ Dependabot Preview has been deactivated ⚠️

This pull request was created by Dependabot Preview, and you've upgraded to Dependabot. This means it won't respond to dependabot commands nor will it be automatically closed if a new version is found.

If you close this pull request, Dependabot will re-create it the next time it checks for updates and everything will work as expected.

---

Bumps github.com/v2fly/v2ray-core/v4 from 4.38.0 to 4.38.2.

Release notes

Sourced from github.com/v2fly/v2ray-core/v4's releases.

v4.38.2

Feature

• FakeDNS: Added fakedns+others sniffer , based on v2fly/v2ray-core#697 . Thanks @​yuhan6665 .
• TLS: A SECURITY improvement that allow the remote peer's TLS certificate to be pinned to a known value. Document for TLS is updated.
• Observatory: A component that measure the connectivity of selected outbounds. The document for Observatory is updated.
• Routing : leastPing balancing strategy is added. This strategy will select a outbound that is alive and completed HTTPS GET request in the least time. The document for Routing is updated.

Fixs

• Fixed crashing in fake dns. v2fly/v2ray-core#931 Thanks @​IceCodeNew
• Added IPv6 pool in fake dns by default. v2fly/v2ray-core#925 Thanks @​Loyalsoldier
• Return ErrEmptyResponse for fakedns. v2fly/v2ray-core#926 Thanks @​sixg0000d
• Fixed UDP DNS connection cause crash. Thanks @​nekohasekai

Chore

• Fixed two typo in comments. Thanks @​U-v-U

Security Advisory

• TLS connections with dangerous diagnose option allowInsecure turn on and without certificate pin with pinnedPeerCertificateChainSha256 will not be able protect your data at all from a attacker in privileged network path(for example ISP or any firewall or censorship infrastructure). This is especially dangerous when an unprotected protocol or option is used, such as any VLess configuration, VMess with none or zero security, and any trojan configuration, in which case your data is accessible to attacker in plain text and attacker can inject arbitrary data pretending to the the remote server. In the case of VLess and trojan, the proxy protocol access control credential is also exposed to the attacker, the attacker will be able to use your proxy. You are advised to use certificate pin (and/or other security features provided in a later version of V2Ray) whenever allowInsecure is turned on. Attempting to MITM your connection temporarily to identify TLS based proxy is a known threat.

Notices

• VMess: From Jan 1, 2022, compatibility for legacy VMess MD5 will be disabled by default. Visit here for more information.
• You are able to compile exactly the same binaries as the ones in Assets section below by simply following the compiling guide.

For downstream developers

The Go module name of v2ray-core has been changed to github.com/v2fly/v2ray-core/v4. Do NOT use v2ray.com/core anymore.

v4.38.1

Feature

• FakeDNS: Added fakedns+others sniffer , based on v2fly/v2ray-core#697 . Thanks @​yuhan6665 .
• TLS: A SECURITY improvement that allow the remote peer's TLS certificate to be pinned to a known value. Document for TLS is updated.
• Observatory: A component that measure the connectivity of selected outbounds. The document for Observatory is updated.
• Routing : leastPing balancing strategy is added. This strategy will select a outbound that is alive and completed HTTPS GET request in the least time. The document for Routing is updated.

Fixs

• Fixed crashing in fake dns. v2fly/v2ray-core#931 Thanks @​IceCodeNew
• Added IPv6 pool in fake dns by default. v2fly/v2ray-core#925 Thanks @​Loyalsoldier
• Return ErrEmptyResponse for fakedns. v2fly/v2ray-core#926 Thanks @​sixg0000d

Chore

• Fixed two typo in comments. Thanks @​U-v-U

Security Advisory

• TLS connections with dangerous diagnose option allowInsecure turn on and without certificate pin with pinnedPeerCertificateChainSha256 will not be able protect your data at all from a attacker in privileged network path(for example ISP or any firewall or censorship infrastructure). This is especially dangerous when an unprotected protocol or option is used, such as any VLess configuration, VMess with none or zero security, and any trojan configuration, in which case your data is accessible to attacker in plain text and attacker can inject arbitrary data pretending to the the remote server. In the case of VLess and trojan, the proxy protocol access control credential is also exposed to the attacker, the attacker will be able to use your proxy. You are advised to use certificate pin (and/or other security features provided in a later version of V2Ray) whenever allowInsecure is turned on. Attempting to MITM your connection temporarily to identify TLS based proxy is a known threat.

... (truncated)

Commits

• 86a3ee2 Update core.go
• 34a98e8 Create CODE_OF_CONDUCT.md (#941)
• dbfc213 fix: make sure the ctx is propagated to connections by detached connection fo...
• d48cf1a fix: make sure the ctx is propagated to connections by detached connection
• 2e26cf6 fix: make sure the ctx is propagated to connections
• 582e903 Update core.go
• a21e4a7 Fix: FakeDNS IPv6 & refine JSON unmarshal (#925)
• bad6cdf Fix: fakedns return ErrEmptyResponse without result (#926)
• 8ba4ac1 fixed a panic issue caused by not checking type of input address in fake dns
• 4737a1f Chore: update dependencies (#920)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)