Skip to content
This repository was archived by the owner on Aug 24, 2021. It is now read-only.

Conversation

@lafe
Copy link

@lafe lafe commented Nov 17, 2017

Starting with .NET 4.7 the GetAsymmetricAlgorithm function of a X509AsymmetricSecurityKey object returns an AsymmetricAlgorithm of type RSACng instead of the previous RSACryptoServiceProvider. Unfortunately, the RSACryptoServiceProvider was hardcoded and therefore, the library breaks on .NET 4.7. This Pull Requests adds compatibility for .NET 4.7 by adding a new SignatureProvider for RSACng and a Factory that creates the correct SignatureProvider based on the encountered AsymmetricAlgorithm.

The .NET version of the project has been raised to .NET 4.6 in order to use the RSACng object, which has been introduced with .NET 4.6. However, the change is behind a conditional compilation flag "NET46", so it is still possible to build the library for .NET 4.5.

@SharePointRadi
Copy link
Collaborator

Hello Lafe,

This is a great submission and we thank you for it. We looked at this with the team and need to make an assessment if it affects anything in the PnP-Core library, especially if we need to plan some work on our nugget packaging. We will look at this further as soon as we get to it.

Thanks!

@SharePointRadi SharePointRadi self-assigned this Dec 6, 2017
@lafe
Copy link
Author

lafe commented Jul 10, 2018

@SharePointRadi Any news regarding this PR?

@lafe
Copy link
Author

lafe commented Feb 20, 2019

@SharePointRadi @VesaJuvonen Do you have any update regarding this PR?

lafe added 3 commits March 6, 2019 14:38
- RSACngProxy can be extended in the future to hold a copy of the key, if necessary
@rjaakke
Copy link

rjaakke commented Jul 7, 2020

Facing the same issue, could really use this PR.
Any news on this?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants