George Kadianakis: > Hello list, > > we've recently been thinking about how to expose onion-service-related > errors to Tor Browser so that we can give more useful error pages to > users. We currently return "Unable to connect" error pages for any kind > of onion service error, and I think we can do better. > > This is a thread to think about the errors we want to expose, how that > should look like, and what options we should give to the users when it > happens. Relevant master tickets are #30022, #30025 and #30000. > > We decided (in #14389) that Tor will export these errors through the > SOCKS port, and the relevant spec is proposal 304 [0]. > > As part of #30090 antonela started making a table of potential > errors. I'm gonna use that in this thread and also add a few more. Hi George, In the hypothetical scenario that Namecoin (or any other naming layer) gets introduced to Tor Browser, it is likely that some error values specific to the naming layer are going to be useful to convey to the user. My preference is to defer that issue until after Namecoin is introduced to Tor Browser (unless you think it's important to prepare for in advance?), but I figured it's worth at least getting it onto your radar. Cheers, -- -Jeremy Rand Lead Application Engineer at Namecoin Mobile email: jeremyrandmobile@xxxxxxxxxx Mobile OpenPGP: 2158 0643 C13B B40F B0FD 5854 B007 A32D AB44 3D9C Send non-security-critical things to my Mobile with OpenPGP. Please don't send me unencrypted messages. My business email jeremy@xxxxxxxxxxx is having technical issues at the moment.
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ tor-dev mailing list tor-dev@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev