We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://blogs.msdn.microsoft.com/windows_hardware_certification/2017/11/13/starting-in-february-2018-packages-signed-using-a-sha-1-digest-algorithm-and-certificate-chain-will-no-longer-be-accepted/
Have started a conversation with @kd8drx, @nlao and @russcam about acquiring a new certificate.
For alpha, have agreed that signing with the Elasticsearch MSI certificate or unsigned are acceptable routes.
The text was updated successfully, but these errors were encountered:
50ffb0d
No branches or pull requests
https://blogs.msdn.microsoft.com/windows_hardware_certification/2017/11/13/starting-in-february-2018-packages-signed-using-a-sha-1-digest-algorithm-and-certificate-chain-will-no-longer-be-accepted/
Have started a conversation with @kd8drx, @nlao and @russcam about acquiring a new certificate.
For alpha, have agreed that signing with the Elasticsearch MSI certificate or unsigned are acceptable routes.
The text was updated successfully, but these errors were encountered: