[tor-bugs] #10416 [Core Tor/Tor]: Tor won't start on Windows when path contains non-ascii characters

Tor Bug Tracker & Wiki blackhole at torproject.org
Tue Aug 27 12:25:02 UTC 2019


#10416: Tor won't start on Windows when path contains non-ascii characters
-------------------------------------------------+-------------------------
 Reporter:  iktsuarpok                           |          Owner:  (none)
     Type:  defect                               |         Status:  new
 Priority:  High                                 |      Milestone:  Tor:
                                                 |  0.4.2.x-final
Component:  Core Tor/Tor                         |        Version:  Tor:
                                                 |  0.2.3.25
 Severity:  Major                                |     Resolution:
 Keywords:  tor-client, windows, unicode,        |  Actual Points:
  win32, tbb-needs, 042-should                   |
Parent ID:  #25729                               |         Points:  1
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by teor):

 Replying to [comment:43 gk]:
 > Replying to [comment:42 teor]:
 > > Is there a sponsor that will fund this work?
 >
 > I have no idea about network-team related sponsors. So, dunno what could
 cover this bug.

 Maybe the bug smash fund could cover this bug?
 It shouldn't take very long to fix.
 Backwards compatibility might be interesting though.

 > > If not, how severe is this issue?
 > > Does it need to be fixed before 0.4.2 stable (December 2019)?
 > > Should we block the 0.4.2 stable release unit it is fixed?
 >
 > This issue has been ongoing for years and is usually quite confusing for
 Windows users. That said the reports we get are not so many. However,
 there is the risk that many more users just think Tor Browser is broken
 and move on.
 >
 > I'd say this bug is not a blocker for 0.4.2 but it would be very nice if
 we could get this fixed, though.

 Ok, that's what 042-should means: we should do this for 0.4.2, but we can
 release without it.

 > Maybe I should tone down my keyword? It's a bit confusing as it seems to
 me that there are different opinions in the network team about which
 keywords to use: IIRC some think we should only use `tbb-needs` and other
 folks think we should have `tbb-needs` and `tbb-wants` to imply priority
 etc. If the latter is (still) the case then this is probably more a `tbb-
 wants` than `tbb-needs`.

 That's not necessary. Most of us seem to use tbb-* as informational
 keywords.

 The keywords that we use to triage bugfixes are 042-should and 042-must.

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


More information about the tor-bugs mailing list