From e0b99c826d88e217b96eb31b5ac83e07e8b4d583 Mon Sep 17 00:00:00 2001 From: Violet Hansen Date: Sat, 18 May 2024 13:40:46 +0300 Subject: [PATCH] Removed the UTF-8 requirement warning It's no longer required https://github.com/MicrosoftDocs/windows-itpro-docs/pull/11889#issuecomment-2105289949 --- .../deployment/create-code-signing-cert-for-wdac.md | 1 - 1 file changed, 1 deletion(-) diff --git a/windows/security/application-security/application-control/windows-defender-application-control/deployment/create-code-signing-cert-for-wdac.md b/windows/security/application-security/application-control/windows-defender-application-control/deployment/create-code-signing-cert-for-wdac.md index 624889e5e4..7c3eabc52d 100644 --- a/windows/security/application-security/application-control/windows-defender-application-control/deployment/create-code-signing-cert-for-wdac.md +++ b/windows/security/application-security/application-control/windows-defender-application-control/deployment/create-code-signing-cert-for-wdac.md @@ -21,7 +21,6 @@ If you have an internal CA, complete these steps to create a code signing certif > - All policies, including base and supplemental, must be signed according to the [PKCS 7 Standard](https://datatracker.ietf.org/doc/html/rfc5652). > - Use RSA keys with 2K, 3K, or 4K key size only. ECDSA isn't supported. > - You can use SHA-256, SHA-384, or SHA-512 as the digest algorithm on Windows 11, as well as Windows 10 and Windows Server 2019 and above after applying the November 2022 cumulative security update. All other devices only support SHA256. -> - Don't use UTF-8 encoding for certificate fields, like 'subject common name' and 'issuer common name'. These strings must be encoded as PRINTABLE_STRING, IA5STRING or BMPSTRING. 1. Open the Certification Authority Microsoft Management Console (MMC) snap-in, and then select your issuing CA.