X500DistinguishedName parsing of friendly names
On Linux and macOS, a distinguished name with a relative distinguished name component that is prefixed with "OID." followed by a friendly name will no longer parse. For example, OID.STREET=MainStreet no longer parses.
Previous behavior
On Linux and macOS only, a distinguished name would successfully parse even if the object identifier (OID) was a friendly name.
New behavior
Attempting to parse a distinguished name with a component prefixed with "OID." but not followed by a well-formed, dotted-decimal OID throws a CryptographicException.
Version introduced
.NET 7
Type of breaking change
This change can affect binary compatibility.
Reason for change
Windows does not permit distinguished names with friendly name OIDs, and that it worked in Linux and macOS was coincidence and not intentional. To bring consistency throughout platforms, the parsing logic was improved to not accept this form.
Recommended action
Change "OID."-prefixed relative distinguished name components to use an OID, such as OID.1.2.3.4=MyValue.
Affected APIs
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for