[tor-bugs] #25729 [Core Tor/Tor]: UTF8 encoded TORRC does NOT parse non-Latin paths

Tor Bug Tracker & Wiki blackhole at torproject.org
Fri Apr 6 11:06:47 UTC 2018


#25729: UTF8 encoded TORRC does NOT parse non-Latin paths
--------------------------+----------------------------------
 Reporter:  Fleming       |          Owner:  (none)
     Type:  defect        |         Status:  closed
 Priority:  Medium        |      Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |        Version:  Tor: unspecified
 Severity:  Normal        |     Resolution:  wontfix
 Keywords:                |  Actual Points:
Parent ID:                |         Points:
 Reviewer:                |        Sponsor:
--------------------------+----------------------------------
Changes (by teor):

 * status:  new => closed
 * resolution:   => wontfix
 * version:  Tor: 0.3.2.10 => Tor: unspecified
 * component:  - Select a component => Core Tor/Tor
 * milestone:   => Tor: unspecified


Comment:

 The Windows fopen() implementation assumes that file paths are in the
 default system encoding, which is win-1252 on the system that created this
 archive.

 Windows does not support UTF-8 as a default system encoding, because its
 system encodings are limited to two bytes per character.

 To support UTF-8 on Windows, tor would need to rewrite all our filesystem
 code to use the Windows unicode filesystem APIs. This would be a breaking
 change for existing configs, and a lot of work for us.

 As a workaround, please save your torrc file in your Windows system
 encoding.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25729#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online


More information about the tor-bugs mailing list