CNG classes don't work on non-windows platforms (#7323)

luizhlelis · web-flow · commit d88edb15de66 · 2021-11-05T13:52:10.000-07:00
diff --git a/xml/System.Security.Cryptography/CngAlgorithm.xml b/xml/System.Security.Cryptography/CngAlgorithm.xml
@@ -53,8 +53,11 @@
   
  Several Cryptography Next Generation (CNG) classes (such as <xref:System.Security.Cryptography.CngKey>) accept <xref:System.Security.Cryptography.CngAlgorithm> objects through an `algorithm` parameter. When the class receives the <xref:System.Security.Cryptography.CngAlgorithm> object, it retrieves the embedded algorithm name by calling the object's <xref:System.Security.Cryptography.CngAlgorithm.Algorithm%2A> property.  
   
- Therefore, <xref:System.Security.Cryptography.CngAlgorithm> serves as an enumeration of well-known algorithms. It lets you specify a well-known algorithm by using a strongly typed value instead of a string.  
-  
+ Therefore, <xref:System.Security.Cryptography.CngAlgorithm> serves as an enumeration of well-known algorithms. It lets you specify a well-known algorithm by using a strongly typed value instead of a string.
+
+> [!NOTE]
+> CNG classes don't work on non-Windows platforms.
+
  ]]></format>
     </remarks>
   </Docs>
diff --git a/xml/System.Security.Cryptography/CngAlgorithmGroup.xml b/xml/System.Security.Cryptography/CngAlgorithmGroup.xml
@@ -54,6 +54,9 @@
  Several Cryptography Next Generation (CNG) classes (such as <xref:System.Security.Cryptography.CngKey>) return <xref:System.Security.Cryptography.CngAlgorithmGroup> objects. Classes that receive <xref:System.Security.Cryptography.CngAlgorithm> objects can retrieve the embedded algorithm group name by calling the object's <xref:System.Security.Cryptography.CngKey.AlgorithmGroup%2A> property.  
   
  Therefore, <xref:System.Security.Cryptography.CngAlgorithmGroup> serves as an enumeration of well-known algorithm groups. It lets you specify an algorithm group name by using a strongly typed value instead of a string.  
+
+> [!NOTE]
+> CNG classes don't work on non-Windows platforms.
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Security.Cryptography/CngKey.xml b/xml/System.Security.Cryptography/CngKey.xml
@@ -39,7 +39,10 @@
   
 ## Remarks  
  This class wraps NCrypt keys, not BCrypt keys. NCrypt is a subset of CNG that provides key storage functionality. BCrypt is a subset that provides base cryptographic services such as random number generation, hash functions, signatures, and encryption keys.  
-  
+
+> [!NOTE]
+> CNG classes don't work on non-Windows platforms.
+
  ]]></format>
     </remarks>
   </Docs>
diff --git a/xml/System.Security.Cryptography/CngKeyBlobFormat.xml b/xml/System.Security.Cryptography/CngKeyBlobFormat.xml
@@ -54,6 +54,9 @@
  Several CNG classes (such as <xref:System.Security.Cryptography.CngKey>) accept <xref:System.Security.Cryptography.CngKeyBlobFormat> objects through a `format` parameter. When the class receives the <xref:System.Security.Cryptography.CngKeyBlobFormat> object, it retrieves the embedded name of the key BLOB format by calling the object's <xref:System.Security.Cryptography.CngKeyBlobFormat.Format%2A> property.  
   
  Therefore, <xref:System.Security.Cryptography.CngKeyBlobFormat> serves as an enumeration of well-known key BLOB formats. It lets you identify a well-known key BLOB format by using a strongly typed value instead of a string.  
+
+> [!NOTE]
+> CNG classes don't work on non-Windows platforms.
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Security.Cryptography/CngKeyCreationParameters.xml b/xml/System.Security.Cryptography/CngKeyCreationParameters.xml
@@ -41,6 +41,9 @@
  You can also add non-standard properties to a key by using the <xref:System.Security.Cryptography.CngKeyCreationParameters.Parameters%2A> property.  
   
  If you need to add properties after a key is created, use the <xref:System.Security.Cryptography.CngKey.SetProperty%2A> method.  
+
+> [!NOTE]
+> CNG classes don't work on non-Windows platforms.
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Security.Cryptography/CngProvider.xml b/xml/System.Security.Cryptography/CngProvider.xml
@@ -54,6 +54,9 @@
  Several CNG classes (such as <xref:System.Security.Cryptography.CngKey>) accept <xref:System.Security.Cryptography.CngProvider> objects through a `provider` parameter. When the class receives the <xref:System.Security.Cryptography.CngProvider> object, it retrieves the embedded provider name by calling the object's <xref:System.Security.Cryptography.CngProvider.Provider%2A> property.  
   
  Therefore, <xref:System.Security.Cryptography.CngProvider> serves as an enumeration of well-known providers. It lets you identify a provider by using a strongly typed value instead of a string.  
+
+> [!NOTE]
+> CNG classes don't work on non-Windows platforms.
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Security.Cryptography/CngUIPolicy.xml b/xml/System.Security.Cryptography/CngUIPolicy.xml
@@ -35,7 +35,10 @@
   
 ## Remarks  
  This class enables you to create a UI policy for displaying prompts about key operations such as smart card PIN prompts. It also enables you to enforce user interaction to access a key, even if the key is stored in a software key storage provider (KSP) instead of in a smart card. CNG displays these configuration parameters for the UI when you access a protected key.  
-  
+
+> [!NOTE]
+> CNG classes don't work on non-Windows platforms.
+ 
  ]]></format>
     </remarks>
   </Docs>
