Jeremy Rand

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 It's likely that for unrelated reasons ncdns will add an authenticated JSON-RPC server (specifically for Tor stream isolation purposes). I think it shouldn't be...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hugo Landau: > @JeremyRand I have no idea what JSON-RPC has to do with this. It was in the context of a "stop" command...

My understanding is that @ryancdotorg agrees with my assessment and proposed stopgap fix -- Ryan, is that accurate?

Some additional notes. Punycode-encoded DNS labels [begin with](https://en.wikipedia.org/wiki/Internationalized_domain_name#ToASCII_and_ToUnicode) `xn--`. So blacklisting all `.bit` domains whose 2nd-level label has that prefix should be sufficient to prevent IDN's from resolving. Various client-side...

> I think blocking them for now is prudent. Okay, thanks. > The best mitigation I've seen is preventing characters from different languages being mixed, but this is complicated. @ryancdotorg...

CC: @josephbisch @hlandau

@hlandau Any idea what's wrong here?

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 I'm curious, have other non-DNS TLD's addressed this issue or analogous ones? For example, does Tor Browser consider .onion URL's to be in a...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 JeremyRand: > I'm curious, have other non-DNS TLD's addressed this issue or > analogous ones? For example, does Tor Browser consider .onion > URL's...

> So, I'm going to defer to the Tor developers on this. If Tor changes their policy on this, or if someone points out to me that I'm incorrect in...