-
Notifications
You must be signed in to change notification settings - Fork 6k
Added additional breaking changes #14386
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Found a few things to fix, one especially bad with incorrect xref tags
Also, the images in the media folder should be in a subfolder with the same name as the article. This makes house keeping easy if the article is deleted or moved in the future.
includes/core-changes/cryptography/better-argument-validation-in-pkcs8privatekeyinfo-ctor.md
Outdated
Show resolved
Hide resolved
includes/core-changes/cryptography/envelopedcms-defaults-to-aes256.md
Outdated
Show resolved
Hide resolved
includes/core-changes/cryptography/envelopedcms-defaults-to-aes256.md
Outdated
Show resolved
Hide resolved
|
||
Starting with .NET Core 3.0 Preview 8 (via version 4.6.0 of the [System.Security.Cryptography.Pkcs](https://www.nuget.org/packages/System.Security.Cryptography.Pkcs/) NuGet package), the default algorithm has been changed to AES-256 for algorithm modernization and to improve the security of default options. If a message recipient certificate has a (non-EC) Diffie-Hellman public key, the encryption operation may fail with a <xref:System.Security.Cryptography.CryptographicException> due to limitations in the underlying platform. | ||
|
||
In the following sample code, the data is encrypted with TripleDES if running on .NET Core 3.0 Preview 7 or earlier. If running on .NET Core 3.0 Preview 8 or later, it is encrypted with AES-257. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the following sample code, the data is encrypted with TripleDES if running on .NET Core 3.0 Preview 7 or earlier. If running on .NET Core 3.0 Preview 8 or later, it is encrypted with AES-257. | |
In the following sample code, the data is encrypted with `TripleDES` if running on .NET Core 3.0 Preview 7 or earlier. If running on .NET Core 3.0 Preview 8 or later, it is encrypted with AES-257. |
|
||
#### Recommended action | ||
|
||
If you are negatively impacted by the change, you can restore TripleDES encryption by explicitly specifying the encryption algorithm identifier in an <xref:System.Security.Cryptography.Pkcs.EnvelopedCms> constructor that includes a parameter of type <xref:System.Security.Cryptography.Pkcs.AlgorithmIdentifier>, such as: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you are negatively impacted by the change, you can restore TripleDES encryption by explicitly specifying the encryption algorithm identifier in an <xref:System.Security.Cryptography.Pkcs.EnvelopedCms> constructor that includes a parameter of type <xref:System.Security.Cryptography.Pkcs.AlgorithmIdentifier>, such as: | |
If you are negatively impacted by the change, you can restore `TripleDES` encryption by explicitly specifying the encryption algorithm identifier in an <xref:System.Security.Cryptography.Pkcs.EnvelopedCms> constructor that includes a parameter of type <xref:System.Security.Cryptography.Pkcs.AlgorithmIdentifier>, such as: |
includes/core-changes/cryptography/minimum-rsaopenssl-key-size-change.md
Outdated
Show resolved
Hide resolved
…-change.md Co-Authored-By: Andy De George <2672110+Thraka@users.noreply.github.com>
6ad716c
to
35cb213
Compare
Added additional breaking changes
Link to internal review site
//cc @PriyaPurkayastha