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

curl/schannel error "SEC_E_ALGORITHM_MISMATCH " getting box from private registry #13365

Open
jjolidon opened this issue Mar 15, 2024 · 1 comment

Comments

@jjolidon
Copy link

Hello,

This error occurs with our private vagrant registry, which currently uses TLS 1.3. This could be related to this curl PR in which case the issue would be that curl is outdated.

Sincerely,
J.

Debug output

Log

Expected behavior

The box is downloaded

Actual behavior

schannel: next InitializeSecurityContext failed: SEC_E_ALGORITHM_MISMATCH (0x80090331) - The client and server cannot communicate, because they do not possess a common algorithm.

Reproduction information

Vagrant add for a server running TLS1.3. The registry is protected by a pfx certificate, but I don't think that's relevant. Firefox can connect, the cipher suite is described as TLS_AES_256_GCM_SHA384, 256 bits keys, TLS 1.3, which seems to correspond to current best practices.

Vagrant version

Vagrant 2.4.1

Host operating system

Windows 10 22H2 19045.4046

Guest operating system

Windows 10 (not relevant)

Steps to reproduce

  1. Use vagrant add to connect to a private repository with https over TLS 1.3

Vagrantfile

N/A

@wyattoday
Copy link

Windows 10 doesn't support proper TLS 1.3. The PR you linked to says as much. Use Windows 11.

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

No branches or pull requests

2 participants