UnicodeDecodeError: 'utf8' codec can't decode bytes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Tahoe-LAFS |
New
|
Unknown
|
|||
pyOpenSSL |
New
|
Undecided
|
Unassigned | ||
python-setuptools |
Unknown
|
Unknown
|
Bug Description
Two different users of Tahoe-LAFS have reported the following symptoms:
User #1, David Abrahams a.k.a. bewst, wrote:
File "/opt/local/
132)
File "/opt/local/
hlreq = CertificateRequ
File "/opt/local/
dn.
File "/opt/local/
value = getattr(x509name, name, None)
UnicodeDecodeError: 'utf8' codec can't decode bytes in position 0-5: unsupported Unicode code range
on this ticket:
http://
User #2, midnightmagic wrote:
File "/v/tahoe/
i386.egg/
hlreq = CertificateRequ
File "/v/tahoe/
i386.egg/
dn.
File "/v/tahoe/
i386.egg/
value = getattr(x509name, name, None)
exceptions.
unsupported Unicode code range
On this ticket:
http://
bewst said that the problem stopped happening when he stopped using one pyOpenSSL package and started using another. I don't know what the status of midnightmagic's problem is.
I guess the next step is to ask bewst for more details about which package of pyOpenSSL fails and which one works.
Changed in allmydata.org: | |
status: | Unknown → New |
Also, could you run the following steps to generate a new certificate and
then examine it to see what the "Subject" names are?
{{{ "dummy. pem")
% python
>>> from foolscap import Tub
>>> t = Tub(certFile=
>>> (Control-D)
% ls dummy.pem
dummy.pem
% openssl x509 -in dummy.pem -text
}}}
On my OS-X system, I see "Subject: CN=newpb_thingy". Do you get the same? It
might also help us if you could attach that dummy.pem file to this ticket
(but of course don't use it for anything else).
My current hunch is that the Foolscap-generated x509 certificates are either
being created with corrupt (i.e. non-UTF-8) subject-name strings, or they're
somehow being corrupted afterwards.