Remove .NET Framework remarks (System.Security.Cryptography) (#12655)

Author: gewarren

xml/System.Security.Cryptography.Pkcs/CmsSigner.xml

@@ -135,24 +135,8 @@
       <Docs>
         <param name="parameters">The CSP parameters to describe which signing key to use.</param>
         <summary>Initializes a new instance of the <see cref="T:System.Security.Cryptography.Pkcs.CmsSigner" /> class from a persisted key.</summary>
-        <remarks>
-          <format type="text/markdown"><![CDATA[
-
-## Remarks
- This constructor results in the following default property values:
-
-|Property|Default value|
-|--------------|-------------------|
-|<xref:System.Security.Cryptography.Pkcs.CmsSigner.SignerIdentifierType*>|<xref:System.Security.Cryptography.Pkcs.SubjectIdentifierType.SubjectKeyIdentifier?displayProperty=nameWithType>|
-|<xref:System.Security.Cryptography.Pkcs.CmsSigner.DigestAlgorithm*>|2.16.840.1.101.3.4.2.1 (SHA-256)|
-|<xref:System.Security.Cryptography.Pkcs.CmsSigner.IncludeOption*>|<xref:System.Security.Cryptography.X509Certificates.X509IncludeOption.None?displayProperty=nameWithType>|
-
-> [!IMPORTANT]
-> This method is only supported on .NET Framework. Its use on .NET Core throws a <xref:System.PlatformNotSupportedException>.
-
- ]]></format>
-        </remarks>
-        <exception cref="T:System.PlatformNotSupportedException">.NET Core and .NET 5+ only: In all cases.</exception>
+        <remarks>To be added.</remarks>
+        <exception cref="T:System.PlatformNotSupportedException">In all cases.</exception>
       </Docs>
     </Member>
     <Member MemberName=".ctor">

xml/System.Security.Cryptography.Pkcs/EnvelopedCms.xml

@@ -107,9 +107,7 @@
 
  The default <xref:System.Security.Cryptography.Pkcs.SubjectIdentifierType> for recipients is <xref:System.Security.Cryptography.Pkcs.SubjectIdentifierType.IssuerAndSerialNumber>.
 
- On .NET Framework, the default symmetric encryption algorithm is determined by the version of the .NET Framework that the application executable was built against. Starting with .NET Framework 4.8, the default algorithm is AES-256 in CBC mode; in prior versions, the default is TripleDES (DES3-EDE) in CBC mode.
-
- On .NET Core, the default symmetric encryption algorithm is determined by the version of the System.Security.Cryptography.Pkcs assembly that is loaded. Starting with the 4.6.0 version of the System.Security.Cryptography.Pkcs NuGet package, the default algorithm is AES-256 in CBC mode; in prior versions, the default is TripleDES (DES3-EDE) in CBC mode.
+The default symmetric encryption algorithm is determined by the version of the System.Security.Cryptography.Pkcs assembly that is loaded. Starting with the 4.6.0 version of the System.Security.Cryptography.Pkcs NuGet package, the default algorithm is AES-256 in CBC mode; in prior versions, the default is TripleDES (DES3-EDE) in CBC mode.
 
  ]]></format>
         </remarks>
@@ -155,10 +153,7 @@
 
  The default <xref:System.Security.Cryptography.Pkcs.SubjectIdentifierType> for recipients is <xref:System.Security.Cryptography.Pkcs.SubjectIdentifierType.IssuerAndSerialNumber>.
 
- On .NET Framework, the default symmetric encryption algorithm is determined by the version of the .NET Framework that the application executable was built against. Starting with .NET Framework 4.8, the default algorithm is AES-256 in CBC mode; in prior versions, the default is TripleDES (DES3-EDE) in CBC mode.
-
- On .NET Core, the default symmetric encryption algorithm is determined by the version of the System.Security.Cryptography.Pkcs assembly that is loaded. Starting with the 4.6.0 version of the System.Security.Cryptography.Pkcs NuGet package, the default algorithm is AES-256 in CBC mode; in prior versions, the default is TripleDES (DES3-EDE) in CBC mode.
-
+The default symmetric encryption algorithm is determined by the version of the System.Security.Cryptography.Pkcs assembly that is loaded. Starting with the 4.6.0 version of the System.Security.Cryptography.Pkcs NuGet package, the default algorithm is AES-256 in CBC mode; in prior versions, the default is TripleDES (DES3-EDE) in CBC mode.
 
  ]]></format>
         </remarks>
@@ -477,11 +472,6 @@
 
 The <xref:System.Security.Cryptography.Pkcs.EnvelopedCms.Decrypt> method does not search the computer My store if it is inaccessible.
 
-The following permissions are required to access the decryption key on .NET Framework:
-
-- <xref:System.Security.Permissions.KeyContainerPermissionFlags.Open?displayProperty=nameWithType>
-- <xref:System.Security.Permissions.KeyContainerPermissionFlags.Decrypt?displayProperty=nameWithType>
-
  ]]></format>
         </remarks>
         <exception cref="T:System.Security.Cryptography.CryptographicException">A cryptographic operation could not be completed.</exception>
@@ -524,16 +514,7 @@ The following permissions are required to access the decryption key on .NET Fram
       <Docs>
         <param name="recipientInfo">The recipient info to use for decryption.</param>
         <summary>Decrypts the contents of the decoded enveloped CMS/PKCS#7 message via a specified recipient info by searching certificate stores for a matching certificate and key.</summary>
-        <remarks>
-          <format type="text/markdown"><![CDATA[
-
-The following permissions are required to access the decryption key on .NET Framework:
-
-- <xref:System.Security.Permissions.KeyContainerPermissionFlags.Open?displayProperty=nameWithType>
-- <xref:System.Security.Permissions.KeyContainerPermissionFlags.Decrypt?displayProperty=nameWithType>
-
- ]]></format>
-        </remarks>
+        <remarks>To be added.</remarks>
         <exception cref="T:System.ArgumentNullException">The <paramref name="recipientInfo" /> parameter is <see langword="null" />.</exception>
         <exception cref="T:System.Security.Cryptography.CryptographicException">A cryptographic operation could not be completed.</exception>
         <exception cref="T:System.InvalidOperationException">A method call was invalid for the object's current state.</exception>
@@ -575,16 +556,7 @@ The following permissions are required to access the decryption key on .NET Fram
       <Docs>
         <param name="extraStore">A collection of certificates to use in addition to the certificate stores for finding a recipient certificate and private key.</param>
         <summary>Decrypts the contents of the decoded enveloped CMS/PKCS#7 message via any available recipient info by searching certificate stores and a provided collection for a matching certificate and key.</summary>
-        <remarks>
-          <format type="text/markdown"><![CDATA[
-
-The following permissions are required to access the decryption key on .NET Framework:
-
-- <xref:System.Security.Permissions.KeyContainerPermissionFlags.Open?displayProperty=nameWithType>
-- <xref:System.Security.Permissions.KeyContainerPermissionFlags.Decrypt?displayProperty=nameWithType>
-
- ]]></format>
-        </remarks>
+        <remarks>To be added.</remarks>
         <exception cref="T:System.ArgumentNullException">The <paramref name="extraStore" /> parameter was <see langword="null" />.</exception>
         <exception cref="T:System.Security.Cryptography.CryptographicException">A cryptographic operation could not be completed.</exception>
         <exception cref="T:System.InvalidOperationException">A method call was invalid for the object's current state.</exception>
@@ -684,16 +656,7 @@ Unlike the other overloads of `Decrypt`, this overload does not search certifica
         <param name="recipientInfo">The recipient info to use for decryption.</param>
         <param name="extraStore">A collection of certificates to use in addition to the certificate stores for finding a recipient certificate and private key.</param>
         <summary>Decrypts the contents of the decoded enveloped CMS/PKCS#7 message via a specified recipient info by searching certificate stores and a provided collection for a matching certificate and key.</summary>
-        <remarks>
-          <format type="text/markdown"><![CDATA[
-
-The following permissions are required to access the decryption key on .NET Framework:
-
-- <xref:System.Security.Permissions.KeyContainerPermissionFlags.Open?displayProperty=nameWithType>
-- <xref:System.Security.Permissions.KeyContainerPermissionFlags.Decrypt?displayProperty=nameWithType>
-
- ]]></format>
-        </remarks>
+        <remarks>To be added.</remarks>
         <exception cref="T:System.ArgumentNullException">The <paramref name="recipientInfo" /> or <paramref name="extraStore" /> parameter is <see langword="null" />.</exception>
         <exception cref="T:System.Security.Cryptography.CryptographicException">A cryptographic operation could not be completed.</exception>
         <exception cref="T:System.InvalidOperationException">A method call was invalid for the object's current state.</exception>

xml/System.Security.Cryptography.Pkcs/SignedCms.xml

@@ -634,11 +634,6 @@
 
 This method succeeds if <xref:System.Security.Cryptography.Pkcs.SubjectIdentifierType.NoSignature?displayProperty=nameWithType> was provided as the `signerIdentifierType` argument of one of the <xref:System.Security.Cryptography.Pkcs.SignedCms> constructor overloads. Otherwise, it throws an exception.
 
-The following permissions are required to access the signature key on .NET Framework:
-
-- <xref:System.Security.Permissions.KeyContainerPermissionFlags.Open?displayProperty=nameWithType>
-- <xref:System.Security.Permissions.KeyContainerPermissionFlags.Sign?displayProperty=nameWithType>
-
  ]]></format>
         </remarks>
         <exception cref="T:System.InvalidOperationException">The recipient certificate is not specified.</exception>
@@ -681,11 +676,6 @@ The following permissions are required to access the signature key on .NET Frame
         <remarks>
           <format type="text/markdown"><![CDATA[
 
-The following permissions are required to access the signature key on .NET Framework:
-
-- <xref:System.Security.Permissions.KeyContainerPermissionFlags.Open?displayProperty=nameWithType>
-- <xref:System.Security.Permissions.KeyContainerPermissionFlags.Sign?displayProperty=nameWithType>
-
 ## Examples
  The following example shows the steps to compute a signature on a <xref:System.Security.Cryptography.Pkcs.SignedCms> message with message content that is not detached. In this case, the message content is included in the <xref:System.Security.Cryptography.Pkcs.SignedCms> message.
 
@@ -737,31 +727,21 @@ The following permissions are required to access the signature key on .NET Frame
       </Parameters>
       <Docs>
         <param name="signer">A <see cref="T:System.Security.Cryptography.Pkcs.CmsSigner" /> object that represents the signer.</param>
-        <param name="silent">.NET Core and .NET 5+ only: <see langword="true" /> to request opening keys with PIN prompts disabled, where supported; otherwise, <see langword="false" />. In .NET Framework, this parameter is not used and a PIN prompt is always shown, if required.</param>
+        <param name="silent"><see langword="true" /> to request opening keys with PIN prompts disabled, where supported; otherwise, <see langword="false" />.</param>
         <summary>Creates a signature using the specified signer and adds the signature to the CMS/PKCS #7 message. </summary>
         <remarks>
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
 
-.NET Core only: The `silent` parameter has no effect if the <xref:System.Security.Cryptography.Pkcs.CmsSigner.PrivateKey?displayProperty=nameWithType> value is not null. The provided value controls whether or not computing the signature shows a PIN prompt. Even when the <xref:System.Security.Cryptography.Pkcs.CmsSigner.PrivateKey> property is null and the `silent` parameter is set to `true`, some combinations of operating system and signer options can still result in a PIN prompt.
-
-The following permissions are required to display the user interface on .NET Framework:
-
-- <xref:System.Security.Permissions.UIPermissionWindow.SafeTopLevelWindows?displayProperty=nameWithType>
-
-The following permissions are required to access the signature key on .NET Framework:
-
-- <xref:System.Security.Permissions.KeyContainerPermissionFlags.Open?displayProperty=nameWithType>
-- <xref:System.Security.Permissions.KeyContainerPermissionFlags.Sign?displayProperty=nameWithType>
+The `silent` parameter has no effect if the <xref:System.Security.Cryptography.Pkcs.CmsSigner.PrivateKey?displayProperty=nameWithType> value is not null. The provided value controls whether or not computing the signature shows a PIN prompt. Even when the <xref:System.Security.Cryptography.Pkcs.CmsSigner.PrivateKey> property is null and the `silent` parameter is set to `true`, some combinations of operating system and signer options can still result in a PIN prompt.
 
  ]]></format>
         </remarks>
         <exception cref="T:System.ArgumentNullException">
           <paramref name="signer" /> is <see langword="null" />.</exception>
         <exception cref="T:System.Security.Cryptography.CryptographicException">A cryptographic operation could not be completed.</exception>
-        <exception cref="T:System.InvalidOperationException">.NET Framework only: A signing certificate is not specified.</exception>
-        <exception cref="T:System.PlatformNotSupportedException">.NET Core and .NET 5+ only: A signing certificate is not specified.</exception>
+        <exception cref="T:System.PlatformNotSupportedException">A signing certificate is not specified.</exception>
       </Docs>
     </Member>
     <Member MemberName="ContentInfo">

xml/System.Security.Cryptography.Pkcs/SignerInfo.xml

@@ -45,7 +45,7 @@
 ## Remarks
  The signatures represented by the <xref:System.Security.Cryptography.Pkcs.SignerInfo> class can be either over message content or a signature. The latter kind of signature is referred to as a *countersignature*.
 
- This implementation of CMS/PKCS #7 supports only one level of countersignature.  That is, a signature can be signed, which forms a countersignature, but that countersignature cannot be signed again.
+ This implementation of CMS/PKCS #7 supports only one level of countersignature. That is, a signature can be signed, which forms a countersignature, but that countersignature cannot be signed again.
 
  This class does not have a public constructor; therefore, it cannot be publicly instantiated. It is a read-only class accessible from the <xref:System.Security.Cryptography.Pkcs.SignedCms.SignerInfos?displayProperty=nameWithType> property.
 
@@ -371,7 +371,7 @@ ASN1 corrupted data.</exception>
 
 ## Remarks
 
-This implementation of CMS/PKCS #7 supports only one level of countersignature.  That is, a signature can be signed, which forms a countersignature, but that countersignature cannot be signed again.
+This implementation of CMS/PKCS #7 supports only one level of countersignature. That is, a signature can be signed, which forms a countersignature, but that countersignature cannot be signed again.
 
 This method displays a user interface in which you choose signers for this message. This requires that the current process is running in *user interactive mode*, meaning that the <xref:System.Environment.UserInteractive?displayProperty=nameWithType> property is set to `true`. A process is normally in user interactive mode unless it is a service process or running inside a Web application.
 
@@ -383,15 +383,6 @@ Signers whose certificates meet the following conditions will be displayed in th
 
 Signer certificates are chosen from the My store.
 
-The following permissions are required to display the user interface on .NET Framework:
-
-- <xref:System.Security.Permissions.UIPermissionWindow.SafeTopLevelWindows?displayProperty=nameWithType>
-
-The following permissions are required to access the signature key on .NET Framework:
-
-- <xref:System.Security.Permissions.KeyContainerPermissionFlags.Open?displayProperty=nameWithType>
-- <xref:System.Security.Permissions.KeyContainerPermissionFlags.Sign?displayProperty=nameWithType>
-
  ]]></format>
         </remarks>
         <exception cref="T:System.ArgumentNullException">A null reference was passed to a method that does not accept it as a valid argument.</exception>
@@ -437,12 +428,7 @@ The following permissions are required to access the signature key on .NET Frame
 
 ## Remarks
 
-This implementation of CMS/PKCS #7 supports only one level of countersignature.  That is, a signature can be signed, which forms a countersignature, but that countersignature cannot be signed again.
-
-The following permissions are required to access the signature key on .NET Framework:
-
-- <xref:System.Security.Permissions.KeyContainerPermissionFlags.Open?displayProperty=nameWithType>
-- <xref:System.Security.Permissions.KeyContainerPermissionFlags.Sign?displayProperty=nameWithType>
+This implementation of CMS/PKCS #7 supports only one level of countersignature. That is, a signature can be signed, which forms a countersignature, but that countersignature cannot be signed again.
 
  ]]></format>
         </remarks>