Project

General

Profile

Actions

Feature #13710

open

Support UTF-8 CA/Certificate subject components

Added by Jim Pingle over 1 year ago. Updated about 2 months ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Certificates
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
24.07
Release Notes:
Default

Description

Some support was added for UTF-8 CA/Certificate fields in #12041 but it isn't complete.

The backend seems to handle UTF-8 in the CN at least, and likely in other fields. Might need to experiment with how/when to use utf8_encode() and utf8_decode() if needed at various times. Quick test of disabling input validation showed that a CA with a CN of møøsë-ca could be created and caused no errors, but some of its components did not display properly in the cert info block.

There are several items to address:

  • Input validation needs relaxed on subject components to allow UTF-8 characters while also preventing characters which are not valid in those fields (CN, org/location fields, SANs)
  • Certain UTF-8 characters are not displayed properly, but running the DN string through utf8_encode() helps. e.g. Creating a CA with a common name of møøsë-ca fails to display properly
  • The method used for handling \x style UTF-8 strings in #12041 also needs to be done for other subject components, in particular the Authority Key ID does not display properly
  • Other areas of the GUI which display and/or utilize CA/Cert subjects or components also need to be checked for similar issues (e.g. cert-based IPsec identifiers)

And potentially more points along those lines that may be revealed during testing and development.

Actions #1

Updated by Jim Pingle about 1 year ago

  • Plus Target Version changed from 23.05 to 23.09
Actions #2

Updated by Jim Pingle 10 months ago

  • Target version changed from 2.7.0 to CE-Next
Actions #3

Updated by Jim Pingle 8 months ago

  • Plus Target Version changed from 23.09 to 24.01

We have enough to worry about with OpenSSL 3.x changes in this release, best not to complicate cert changes any further. Moving ahead.

Actions #4

Updated by Jim Pingle 7 months ago

  • Plus Target Version changed from 24.01 to 24.03
Actions #5

Updated by Jim Pingle about 2 months ago

  • Plus Target Version changed from 24.03 to 24.07
Actions

Also available in: Atom PDF