Re: Fwd: TLS/SSH bugs

On 10 Dec 2014 at 14:43, Peter Gutmann wrote:

> David Harris <[email protected]> writes:
> 
> >It's easy to use UTF-8 in Windows: just use the MultiByteToWideChar
> >and WideCharToMultiByte functions with the CP_UTF8 code page to
> >convert between unicode or ACP and UTF-8.
> 
> That's only how to do it programmatically though, not how it was
> originally created. The Windows native character sets are Windows/OEM
> code pages or Unicode, not UTF8, so whatever got fed to cryptlib would
> presumably have been a particular Windows code page or Unicode, not
> UTF8.

I'm not sure why you say that. Given how easy it is to do the conversion, I would 
expect it would be commonplace for programs to perform the conversion as part of 
the process of creating the certificate - I know it's what I do, simply because I know 
UTF-8 is so prevalent now.

Any program I write now routinely takes either the ACP or Unicode data from the 
Windows dialogs and converts it into UTF-8 before storing or actioning it - in e-mail 
and almost anything to do with the web this is just what you have to do these days.

Surely it's no stretch to imagine other people doing the same thing?

Cheers!

-- David --

------------------ David Harris -+- Pegasus Mail ----------------------
Box 5451, Dunedin, New Zealand | e-mail: [email protected]
           Phone: +64 3 453-6880 | Fax: +64 3 453-6612

Real newspaper headlines from US Papers:
   "Three ambulances take blast victim to hospital".



_______________________________________________
Cryptlib mailing list
[email protected] via Mail: [email protected]
Archive: ftp://ftp.franken.de/pub/crypt/cryptlib/archives/
http://news.gmane.org/gmane.comp.encryption.cryptlib
Posts from non-subscribed addresses are blocked to prevent spam, please
subscribe in order to post messages.