[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn fails to handle certificates with non-ascii characters

From: Joe Orton <joe_at_manyfish.co.uk>
Date: 2004-02-10 15:39:10 CET

On Tue, Feb 10, 2004 at 01:03:56PM +0100, Anders Blomdell wrote:
> When svn is presented a certificate that contains non ASCII characters, it
> fails to present a proper user override.

Yes, really it's a neon issue, neon completely ignores the ASN.1 types
of the attributes in the cert DN, so will pass back UCS-4 or ASCII or
whatever the cert uses. neon should define ne_ssl_readable_dname() to
return only UTF-8 strings, and convert, reject, or strip input

Note that PKIX now mandates use of UTF-8 in newly created certs from
2004 onwards... and that technically your cert is badly encoded (like
many others), since it puts an ISO-8859-1 string in a T61String object.

Bottom line: if you stick to ASCII or UTF-8 in your cert DNs, it will
happen to work correctly; otherwise, all bets are off.



To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Feb 10 15:39:32 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.