[tor-bugs] #30558 [Applications/Tor Browser]: Namecoin support for onion sites in Tor Browser

[Tor Bug Tracker & Wiki]

#30558: Namecoin support for onion sites in Tor Browser
--------------------------------------+--------------------------------
 Reporter:  arthuredelstein           |          Owner:  JeremyRand
     Type:  defect                    |         Status:  needs_revision
 Priority:  Medium                    |      Milestone:
Component:  Applications/Tor Browser  |        Version:
 Severity:  Normal                    |     Resolution:
 Keywords:  TorBrowserTeam201912      |  Actual Points:
Parent ID:                            |         Points:
 Reviewer:  gk                        |        Sponsor:
--------------------------------------+--------------------------------

Comment (by gk):

 Replying to [comment:49 JeremyRand]:
 > > JeremyRand: Are those domains you mentioned in comment:7 still up and
 running? None of them works for me. If not, where are domains that are
 supposed to be up and working?
 >
 > @gk All 4 of those domains work fine for me as of just now.  Just to
 verify, you're running the GNU/Linux nightly build with the environment
 variable `TOR_ENABLE_NAMECOIN=1`, right?  Are you on x86_64 or i686?  What
 version of Python is installed?  Can you provide the output that you get
 if you run Tor Browser from a terminal with the `--verbose` flag, and then
 try to visit one of the 4 domains I listed?

 That's been with a custom build which is nightly-ish, yes. Python 3.7.5
 with `TOR_ENABLE_NAMECOIN=1`. I try to reproduce the issue but meanwhile
 another problem I've seen is that Namecoin enabled is sometimes hammering
 the Tor network with stream creations like attached in the log which is
 very concerning. The latter at least could be related to Namecoin not
 properly shutting down when I close the browser e.g. by pressing Ctrl+C in
 my terminal. The result is that I can't stop the remaining Python process
 by either pressing Ctrl+C further or closing the terminal. Additionally,
 it has the interesting property that it messes with a newly started Tor
 Browser in a new terminal even though `TOR_ENABLE_NAMECOIN` is *not* set
 there, rendering that Tor Browser non-functional and one can see requests
 to `ulrichard.ch` in that terminal. That's not supposed to happen.

 So, at the end my trouble connecting to a .bit domain might result in the
 above bug but I am not sure yet.

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