-
Notifications
You must be signed in to change notification settings - Fork 922
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
New certificate fails to load after creation 'The specified network password is not correct' #1670
Labels
bug
A bug was identified and should be fixed.
Comments
see also @ZbynekZ Not sure if the issue has the same root cause and if it gets improved by this workaround. Maybe permission also affect the timing. But in the windows container the MachineKeySet is not accessible. |
This was referenced Jan 22, 2022
mregen
added a commit
that referenced
this issue
Jan 24, 2022
- In windows container this non deterministic error can occur: `[WindowsCryptographicException] The specified network password is not correct.` even if the private key was saved with empty password. - Fix: After a delayed retry the private key can be loaded successfully. - fixes #1670 - see also ae9ecac for 367 milestone
mregen
added a commit
that referenced
this issue
Jan 25, 2022
- integrate 'LoadPrivateKey' in the interface to allow to implement cert stores which require a passcode to load/store certificates Change of behavior: - Introduce a 'NoPrivateKeys' flag to reduce the risk of leaking a private key to a unsecure store. - CertificateStoreIdentifier opens 'NoPrivateKey' stores - CertificateTrustList opens 'NoPrivateKey' stores - CertificateIdentifier opens store with private keys for application or GDS authority certificates - CertificateTrustList reuses a store if it is not disposed. A user can just close the store to keep the list of certificates in memory. - DirectoryStore `Load` does not read private keys anymore, only file names for delete. Reading all private keys caused false errors, e.g. here: #1670 Co-authored-by: mheege-abb <marcus.heege@de.abb.com> Co-authored-by: mheege-abb <85437567+mheege-abb@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Type of Issue
-[X] Bug
Describe the Issue
Running a .NET Core 3 UA application in docker windows container sometimes fails to start when a new application certificate is created with error: 'The specified network password is not correct'. The container starts ok using the same previously created certificate when restarted.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
New cert can be loaded.
Screenshots
If applicable, add screenshots to help explain your problem.
Code snippets
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: