You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a PROTOCOLINFO's authentication cookie path mismatches our filesystem
encoding falling back to a couple common encodings (unicode and latin-1).
#57
Hi ZeroNet, sorry for taking so long to get to this. The problem is that your filesystem is configured as unicode whereas that path is latin-1. For example, the first non-ascii character is an 'a' with an umlaut...
>>> b"\341".decode('utf-8')
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe1 in position 0: unexpected end of data
>>> b"\341".decode('latin-1')
'á'
I just pushed a patch so we attempt to parse these paths as both unicode and latin-1 when our filesystem encoding doesn't work.
Stem version: 1.8.0
Python version: 3.7.3
Tor: 0.4.2.6 (git-971a6beff5a53434) running on Windows 8 [or later] with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma N/A, and Libzstd N/A.
Starting tor.exe:
torrc-defaults file:
Script:
PROTOCOLINFO result:
The text was updated successfully, but these errors were encountered: