into browser's
profile.
Probably adding -utf8 option for x509 command should fix this particular
issue.
P.S. I use =dev-libs/openssl-1.0.1k amd64 build on Gentoo GNU/Linux.
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org
because mail list seems to reject such
letters)
displays utf8 symbol codes instead of expected human-readably letters (in this
case — cyrillic), shown after import this certificate into browser's profile.
Probably adding -utf8 option for x509 command should fix this particular issue.
P.S. I
list seems to reject such
letters)
displays utf8 symbol codes instead of expected human-readably letters (in this
case — cyrillic), shown after import this certificate into browser's profile.
Probably adding -utf8 option for x509 command should fix this particular issue.
P.S. I use =dev-libs
On 02-03-26 12:09:59 CET, Robert Joop wrote:
On 02-03-25 18:03:56 CET, Stephen Sprunk wrote:
Here's the more interesting question: why do we have a switch for
UTF-8 encoding, instead of determining it from the user's locale?
what is the canonical way to detect this?
following up to
At 01:14 PM 3/26/02 +0100, you wrote:
On 02-03-26 12:09:59 CET, Robert Joop wrote:
On 02-03-25 18:03:56 CET, Stephen Sprunk wrote:
Here's the more interesting question: why do we have a switch for
UTF-8 encoding, instead of determining it from the user's locale?
what is the canonical
On 02-03-26 15:01:37 CET, George Rogers wrote:
Have you guys forgotten that the client and server are on different ends of
the
wire? Which end of the wire is going to use the certificate? Which end of
the
wire is creating the certificate? The switch has to be there to allow
creation
the explanation of the -utf8 option doesn't make sense, does it?
quote src=http://www.openssl.org/docs/apps/req.html;
-utf8
this option causes field values to be interpreted as UTF8 strings, by default they
are interpreted as ASCII. This means that the field values, whether prompted from
Thus spake Robert Joop:
the explanation of the -utf8 option doesn't make sense, does it?
quote src=http://www.openssl.org/docs/apps/req.html;
-utf8
this option causes field values to be interpreted as UTF8 strings, by default
they are interpreted as ASCII. This means that the field
