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

[Tor Bug Tracker & Wiki]

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

 * parent:  #27380 =>


Comment:

 Unparenting, we do not need to make the torrc UTF-8 yet.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

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

Comment (by teor):

 Here is one possible scheme:
 * tor defaults to using the default codepage for filenames
 * add a torrc option, extra option argument, or filename prefix that makes
 tor use the specified codepage or UTF-8

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

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

 * parent:   => #27380


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

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

 * keywords:   => needs-proposal


Comment:

 This has potential backwards compatibility and security implications, so
 it needs a proposal.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

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

 * keywords:  needs-proposal =>


Comment:

 Am not a developer, but my user’s experience says that DataDirectory path
 is a string, right? Check its existence on disk as ANSI first, then
 internally convert that string to UTF8 and check again.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

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

 * keywords:   => needs-proposal
 * status:  closed => reopened
 * resolution:  wontfix =>


Comment:

 If anyone wants to have a go, here is a reference:
 https://stackoverflow.com/questions/2050973/what-encoding-are-filenames-
 in-ntfs-stored-as

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#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:
--+--

Comment (by Fleming):

 Win1252? ANSI codepage which was used is Win1251.
 Also I have tried setting “chcp 65001” before running UTF8 encoded torrc,
 didn’t help.
 Let other developers take a peek, why the rush?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#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: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs