https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162016-11-04T11:22:49ZpfSense bugtrackerpfSense - Bug #6432: Relative distinguished names should accept unicode during CA creation.https://redmine.pfsense.org/issues/6432?journal_id=292472016-11-04T11:22:49ZSean McBride
<ul></ul><p>I hit this exact problem too.</p>
<p>It would be nice to at least improve the error message to state which characters are currently allowed. I'll take a stab at creating such a patch...</p> pfSense - Bug #6432: Relative distinguished names should accept unicode during CA creation.https://redmine.pfsense.org/issues/6432?journal_id=313002017-02-10T10:23:19ZJim Pingle
<ul><li><strong>Target version</strong> set to <i>2.3.3</i></li></ul> pfSense - Bug #6432: Relative distinguished names should accept unicode during CA creation.https://redmine.pfsense.org/issues/6432?journal_id=314322017-02-10T13:27:29ZRenato Botelhorenato@netgate.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li></ul><p>works</p> pfSense - Bug #6432: Relative distinguished names should accept unicode during CA creation.https://redmine.pfsense.org/issues/6432?journal_id=314352017-02-10T13:52:01ZSean McBride
<ul></ul><p>To be clear, what's the fix? Does it merely warn to use only ASCII, or does it now support Unicode properly?</p> pfSense - Bug #6432: Relative distinguished names should accept unicode during CA creation.https://redmine.pfsense.org/issues/6432?journal_id=317002017-02-21T06:21:46ZMarcel Hellwigpfsense@cookiesoft.de
<ul></ul><p>If you look at the associated revisions you'll see, that he only wants <code>A-Z, a-z, space, underscore, and dash</code></p>
<p>That's not a solution for this problem!</p> pfSense - Bug #6432: Relative distinguished names should accept unicode during CA creation.https://redmine.pfsense.org/issues/6432?journal_id=321612017-03-14T15:19:29ZJim Thompsonjim@netgate.com
<ul><li><strong>Assignee</strong> set to <i>Anonymous</i></li></ul>