Policy-Discussion

[Philipp Gühring <pg AT futureware.at>]

Hi,

> > If there are still issues with CAcert certificates and UTF-8 I think we
> > should (better: we have to) provide a possibility to avoid these issues.
> > Either by making the certificates working with UTF-8 or by allowing
> > transliteration of problematic characters.
>
> Hmm.  Good point.  OK, so what does the system do if your
> name includes an umlaut?

The system currently stores the umlaut in iso-8859-1, which can be used with 
X.509, but it breaks OpenPGP.

http://wiki.cacert.org/wiki/UnicodeTaskForce
> > Another problem are the Certificates itself. If I remember correctly
> > there have been some issues about UTF-8 and X.509 certificates...
> > And if we allow substitution of loacal special chars into some
> > ASCII-counterpart we would need a comprehensive list of allowed
> > substitutions.
>
> Yes, ok so potentially we have:
>
> User's Name(s) ==> CAcert-assigned Name(s) ==> x.509 Name(s)

And then we have x.509 Name(s)  ==> different interpretations by various 
applications

(Non-repudiation at it´s best *g*)

Best regards,
Philipp Gühring