Use latest cryptography #16
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I've built npm with (amd64 and arm64) with cryptography 38, all work as intended. Is there any reason, why we should stay on 2.8?
|
Docker Image for build 1 is available on DockerHub as:
|
|
Yes there was, it was related to the certbot plugins. Most of them (at the time) were failing because of the crypto package. This might not be an issue anymore, but it would need to be tested at length with the nginx-proxy-manager project |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've built npm with (amd64 and arm64) with cryptography 38, all work as intended. Is there any reason, why we should stay on 2.8?