Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v5 config pinned_peer_certificate_chain_sha256 not working #3081

Open
mkmark opened this issue Jul 18, 2024 · 0 comments
Open

v5 config pinned_peer_certificate_chain_sha256 not working #3081

mkmark opened this issue Jul 18, 2024 · 0 comments

Comments

@mkmark
Copy link
Contributor

mkmark commented Jul 18, 2024

v5 config pinned_peer_certificate_chain_sha256 not working unless allowInsecure is true, which is impossible because

bool allow_insecure = 1 [(v2ray.core.common.protoext.field_opt).forbidden = true];

When allowInsecure is false, tls error tls: failed to verify certificate: x509: certificate signed by unknown authority] > common/retry: all retry attempts failed happens before pinned_peer_certificate_chain_sha256 is checked.

Technically, even with pinned_peer_certificate_chain_sha256 it's still insecure, so is indeed allowInsecure = True.

Moreover, allowInsecure should be a feature, there should be no need to block users from using that. If one is indeed concerned about users' welfare, the logic should be requiring both allowInsecure and a correct pinned_peer_certificate_chain_sha256 in the config.

Pending pull request will simply reenable allowInsecure, for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant