Remove BouncyCastle dependency to use System.Security.Cryptography #75
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
change dotnet version
fix .net version
fix .net version
|
Hi, Thanks for this work. I look at merging this in however it uses a few APIs that are only available on windows. I would love to replace them with cross platform alternatives once i get some time to get this merged in. |
Looks good! Could you please remove .net48 and do the cryptography in .net core only |
|
Any news on this? Would like to see a version with System.Security.Cryptography only :) |
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.
Remove BouncyCastle dependency to use System.Security.Cryptography.
Add .net48 support
Remove .netstandard1.1 et .netstandard2.0 don't support all crypto methods